Cancellation Indication and Cell Deactivation

ABSTRACT

A wireless device may receive cancellation indication configuration parameters and a second configuration parameter. The cancellation indication configuration parameters may comprise a first configuration parameter indicating a first RNTI. The second configuration parameter may indicate a value of a deactivation timer of a secondary cell. The wireless device may receive a cancellation indication DCI associated with the first RNTI. The cancellation indication DCI may indicate cancellation of an uplink transmission on the secondary cell. Based on receiving the cancellation indication DCI, the wireless device may start the deactivation timer with the value. The wireless device may deactivate the secondary cell based on the deactivation timer expiring.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/200,953, filed Mar. 15, 2021, which is a continuation of U.S. patentapplication Ser. No. 17/090,549, filed Nov. 5, 2020, which claims thebenefit of U.S. Provisional Application No. 62/932,485, filed Nov. 7,2019, which is hereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B show examples of mobile communications systems inaccordance with several of various embodiments of the presentdisclosure.

FIG. 2A and FIG. 2B show examples of user plane and control planeprotocol layers in accordance with several of various embodiments of thepresent disclosure.

FIG. 3 shows example functions and services offered by protocol layersin a user plane protocol stack in accordance with several of variousembodiments of the present disclosure.

FIG. 4 shows example flow of packets through the protocol layers inaccordance with several of various embodiments of the presentdisclosure.

FIG. 5A shows example mapping of channels between layers of the protocolstack and different physical signals in downlink in accordance withseveral of various embodiments of the present disclosure.

FIG. 5B shows example mapping of channels between layers of the protocolstack and different physical signals in uplink in accordance withseveral of various embodiments of the present disclosure.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure.

FIG. 7 shows examples of RRC states and RRC state transitions inaccordance with several of various embodiments of the presentdisclosure.

FIG. 8 shows an example time domain transmission structure in NR bygrouping OFDM symbols into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure.

FIG. 10 shows example adaptation and switching of bandwidth parts inaccordance with several of various embodiments of the presentdisclosure.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure.

FIG. 13A shows example time and frequency structure of SSBs and theirassociations with beams in accordance with several of variousembodiments of the present disclosure.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure.

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processesin accordance with several of various embodiments of the presentdisclosure.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure.

FIG. 16 shows an example uplink cancellation process in accordance withan aspect of an embodiment of the present disclosure.

FIG. 17 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 18 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 19 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 20 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 21 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 22 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 23 shows an example uplink cancellation indication process inaccordance with an aspect of an embodiment of the present disclosure.

FIG. 24 shows an example secondary cell deactivation process inaccordance with an aspect of an embodiment of the present disclosure.

FIG. 25 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 26 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

DETAILED DESCRIPTION

The exemplary embodiments of the disclosed technology enable uplinkcancellation indication operation in a wireless device and/or one ormore base stations. The exemplary disclosed embodiments may beimplemented in the technical field of wireless communication systems.More particularly, the embodiment of the disclosed technology may relateto monitoring control channel for uplink cancellation indication.

The devices and/or nodes of the mobile communications system disclosedherein may be implemented based on various technologies and/or variousreleases/versions/amendments of a technology. The various technologiesinclude various releases of long-term evolution (LTE) technologies,various releases of 5G new radio (NR) technologies, various wirelesslocal area networks technologies and/or a combination thereof and/oralike. For example, a base station may support a given technology andmay communicate with wireless devices with different characteristics.The wireless devices may have different categories that define theircapabilities in terms of supporting various features. The wirelessdevice with the same category may have different capabilities. Thewireless devices may support various technologies such as variousreleases of LTE technologies, various releases of 5G NR technologiesand/or a combination thereof and/or alike. At least some of the wirelessdevices in the mobile communications system of the present disclosuremay be stationary or almost stationary. In this disclosure, the terms“mobile communications system” and “wireless communications system” maybe used interchangeably.

FIG. 1A shows an example of a mobile communications system 100 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 100 may be, for example,run by a mobile network operator (MNO) or a mobile virtual networkoperator (MVNO). The mobile communications system 100 may be a publicland mobile network (PLMN) run by a network operator providing a varietyof service including voice, data, short messaging service (SMS),multimedia messaging service (MMS), emergency calls, etc. The mobilecommunications system 100 includes a core network (CN) 106, a radioaccess network (RAN) 104 and at least one wireless device 102.

The CN 106 connects the RAN 104 to one or more external networks (e.g.,one or more data networks such as the Internet) and is responsible forfunctions such as authentication, charging and end-to-end connectionestablishment. Several radio access technologies (RATs) may be served bythe same CN 106.

The RAN 104 may implement a RAT and may operate between the at least onewireless device 102 and the CN 106. The RAN 104 may handle radio relatedfunctionalities such as scheduling, radio resource control, modulationand coding, multi-antenna transmissions and retransmission protocols.The wireless device and the RAN may share a portion of the radiospectrum by separating transmissions from the wireless device to the RANand the transmissions from the RAN to the wireless device. The directionof the transmissions from the wireless device to the RAN is known as theuplink and the direction of the transmissions from the RAN to thewireless device is known as the downlink. The separation of uplink anddownlink transmissions may be achieved by employing a duplexingtechnique. Example duplexing techniques include frequency divisionduplexing (FDD), time division duplexing (TDD) or a combination of FDDand TDD.

In this disclosure, the term wireless device may refer to a device thatcommunicates with a network entity or another device using wirelesscommunication techniques. The wireless device may be a mobile device ora non-mobile (e.g., fixed) device. Examples of the wireless deviceinclude cellular phone, smart phone, tablet, laptop computer, wearabledevice (e.g., smart watch, smart shoe, fitness trackers, smart clothing,etc.), wireless sensor, wireless meter, extended reality (XR) devicesincluding augmented reality (AR) and virtual reality (VR) devices,Internet of Things (IoT) device, vehicle to vehicle communicationsdevice, road-side units (RSU), automobile, relay node or any combinationthereof. In some examples, the wireless device (e.g., a smart phone,tablet, etc.) may have an interface (e.g., a graphical user interface(GUI)) for configuration by an end user. In some examples, the wirelessdevice (e.g., a wireless sensor device, etc.) may not have an interfacefor configuration by an end user. The wireless device may be referred toas a user equipment (UE), a mobile station (MS), a subscriber unit, ahandset, an access terminal, a user terminal, a wireless transmit andreceive unit (WTRU) and/or other terminology.

The at least one wireless device may communicate with at least one basestation in the RAN 104. In this disclosure, the term base station mayencompass terminologies associated with various RATs. For example, abase station may be referred to as a Node B in a 3G cellular system suchas Universal Mobile Telecommunication Systems (UMTS), an evolved Node B(eNB) in a 4G cellular system such as evolved universal terrestrialradio access (E-UTRA), a next generation eNB (ng-eNB), a Next GenerationNode B (gNB) in NR and/or a 5G system, an access point (AP) in Wi-Fiand/or other wireless local area networks. A base station may bereferred to as a remote radio head (RRH), a baseband unit (BBU) inconnection with one or more RRHs, a repeater or relay for coverageextension and/or any combination thereof. In some examples, all protocollayers of a base station may be implemented in one unit. In someexample, some of the protocol layers (e.g., upper layers) of the basestation may be implemented in a first unit (e.g., a central unit (CU))and some other protocol layer (e.g., lower layers) may be implemented inone or more second units (e.g., distributed units (DUs)).

A base station in the RAN 104 includes one or more antennas tocommunicate with the at least one wireless device. The base station maycommunicate with the at least one wireless device using radio frequency(RF) transmissions and receptions via RF transceivers. The base stationantennas may control one or more cells (or sectors). The size and/orradio coverage area of a cell may depend on the range that transmissionsby a wireless device can be successfully received by the base stationwhen the wireless device transmits using the RF frequency of the cell.The base station may be associated with cells of various sizes. At agiven location, the wireless device may be in coverage area of a firstcell of the base station and may not be in coverage area of a secondcell of the base station depending on the sizes of the first cell andthe second cell.

A base station in the RAN 104 may have various implementations. Forexample, a base station may be implemented by connecting a BBU (or a BBUpool) coupled to one or more RRHs and/or one or more relay nodes toextend the cell coverage. The BBU pool may be located at a centralizedsite like a cloud or data center. The BBU pool may be connected to aplurality of RRHs that control a plurality of cells. The combination ofBBU with the one or more RRHs may be referred to as a centralized orcloud RAN (C-RAN) architecture. In some implementations, the BBUfunctions may be implemented on virtual machines (VMs) on servers at acentralized location. This architecture may be referred to as virtualRAN (vRAN). All, most or a portion of the protocol layer functions(e.g., all or portions of physical layer, medium access control (MAC)layer and/or higher layers) may be implemented at the BBU pool and theprocessed data may be transmitted to the RRHs for further processingand/or RF transmission. The links between the BBU pool and the RRHs maybe referred to as fronthaul.

In some deployment scenarios, the RAN 104 may include macrocell basestations with high transmission power levels and large coverage areas.In other deployment scenarios, the RAN 104 may include base stationsthat employ different transmission power levels and/or have cells withdifferent coverage areas. For example, some base station may bemacrocell base stations with high transmission powers and/or largecoverage areas and other base station may be small cell base stationswith comparatively smaller transmission powers and/or coverage areas. Insome deployment scenarios, a small cell base station may have coveragethat is within or has overlap with coverage area of a macrocell basestation. A wireless device may communicate with the macrocell basestation while within the coverage area of the macrocell base station.For additional capacity, the wireless device may communicate with boththe macrocell base station and the small cell base station while in theoverlapped coverage area of the macrocell base station and the smallcell base station. Depending on their coverage areas, a small cell basestation may be referred to as a microcell base station, a picocell basestation, a femtocell base station or a home base station.

Different standard development organizations (SDOs) have specified, ormay specify in future, mobile communications systems that have similarcharacteristics as the mobile communications system 100 of FIG. 1A. Forexample, the Third-Generation Partnership Project (3GPP) is a group ofSDOs that provides specifications that define 3GPP technologies formobile communications systems that are akin to the mobile communicationssystem 100. The 3GPP has developed specifications for third generation(3G) mobile networks, fourth generation (4G) mobile networks and fifthgeneration (5G) mobile networks. The 3G, 4G and 5G networks are alsoknown as Universal Mobile Telecommunications System (UMTS), Long TermEvolution (LTE) and 5G system (5GS), respectively. In this disclosure,embodiments are described with respect to the RAN implemented in a 3GPP5G mobile network that is also referred to as next generation RAN(NG-RAN). The embodiments may also be implemented in other mobilecommunications systems such as 3G or 4G mobile networks or mobilenetworks that may be standardized in future such as sixth generation(6G) mobile networks or mobile networks that are implemented bystandards bodies other than 3GPP. The NG-RAN may be based on a new RATknown as new radio (NR) and/or other radio access technologies such asLTE and/or non-3GPP RATs.

FIG. 1B shows an example of a mobile communications system 110 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 110 of FIG. 1B is anexample of a 5G mobile network and includes a 5G CN (5G-CN) 130, anNG-RAN 120 and UEs (collectively 112 and individually UE 112A and UE112B). The 5G-CN 130, the NG-RAN 120 and the UEs 112 of FIG. 1B operatesubstantially alike the CN 106, the RAN 104 and the at least onewireless device 102, respectively, as described for FIG. 1A.

The 5G-CN 130 of FIG. 1B connects the NG-RAN 120 to one or more externalnetworks (e.g., one or more data networks such as the Internet) and isresponsible for functions such as authentication, charging andend-to-end connection establishment. The 5G-CN has new enhancementscompared to previous generations of CNs (e.g., evolved packet core (EPC)in the 4G networks) including service-based architecture, support fornetwork slicing and control plane/user plane split. The service-basedarchitecture of the 5G-CN provides a modular framework based on serviceand functionalities provided by the core network wherein a set ofnetwork functions are connected via service-based interfaces. Thenetwork slicing enables multiplexing of independent logical networks(e.g., network slices) on the same physical network infrastructure. Forexample, a network slice may be for mobile broadband applications withfull mobility support and a different network slice may be fornon-mobile latency-critical applications such as industry automation.The control plane/user plane split enables independent scaling of thecontrol plane and the user plane. For example, the control planecapacity may be increased without affecting the user plane of thenetwork.

The 5G-CN 130 of FIG. 1B includes an access and mobility managementfunction (AMF) 132 and a user plane function (UPF) 134. The AMF 132 maysupport termination of non-access stratum (NAS) signaling, NAS signalingsecurity such as ciphering and integrity protection, inter-3GPP accessnetwork mobility, registration management, connection management,mobility management, access authentication and authorization andsecurity context management. The NAS is a functional layer between a UEand the CN and the access stratum (AS) is a functional layer between theUE and the RAN. The UPF 134 may serve as an interconnect point betweenthe NG-RAN and an external data network. The UPF may support packetrouting and forwarding, packet inspection and Quality of Service (QoS)handling and packet filtering. The UPF may further act as a ProtocolData Unit (PDU) session anchor point for mobility within and betweenRATs.

The 5G-CN 130 may include additional network functions (not shown inFIG. 1B) such as one or more Session Management Functions (SMFs), aPolicy Control Function (PCF), a Network Exposure Function (NEF), aUnified Data Management (UDM), an Application Function (AF), and/or anAuthentication Server Function (AUSF). These network functions alongwith the AMF 132 and UPF 134 enable a service-based architecture for the5G-CN.

The NG-RAN 120 may operate between the UEs 112 and the 5G-CN 130 and mayimplement one or more RATs. The NG-RAN 120 may include one or more gNBs(e.g., gNB 122A or gNB 122B or collectively gNBs 122) and/or one or moreng-eNBs (e.g., ng-eNB 124A or ng-eNB 124B or collectively ng-eNB s 124).The general terminology for gNB s 122 and/or an ng-eNBs 124 is a basestation and may be used interchangeably in this disclosure. The gNBs 122and the ng-eNBs 124 may include one or more antennas to communicate withthe UEs 112. The one or more antennas of the gNB s 122 or ng-eNBs 124may control one or more cells (or sectors) that provide radio coveragefor the UEs 112.

A gNB and/or an ng-eNB of FIG. 1B may be connected to the 5G-CN 130using an NG interface. A gNB and/or an ng-eNB may be connected withother gNBs and/or ng-eNBs using an Xn interface. The NG or the Xninterfaces are logical connections that may be established using anunderlying transport network. The interface between a UE and a gNB orbetween a UE and an ng-eNBs may be referred to as the Uu interface. Aninterface (e.g., Uu, NG or Xn) may be established by using a protocolstack that enables data and control signaling exchange between entitiesin the mobile communications system of FIG. 1B. When a protocol stack isused for transmission of user data, the protocol stack may be referredto as user plane protocol stack. When a protocol stack is used fortransmission of control signaling, the protocol stack may be referred toas control plane protocol stack. Some protocol layer may be used in bothof the user plane protocol stack and the control plane protocol stackwhile other protocol layers may be specific to the user plane or controlplane.

The NG interface of FIG. 1B may include an NG-User plane (NG-U)interface between a gNB and the UPF 134 (or an ng-eNB and the UPF 134)and an NG-Control plane (NG-C) interface between a gNB and the AMF 132(or an ng-eNB and the AMF 132). The NG-U interface may providenon-guaranteed delivery of user plane PDUs between a gNB and the UPF oran ng-eNB and the UPF. The NG-C interface may provide services such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission.

The UEs 112 and a gNB may be connected using the Uu interface and usingthe NR user plane and control plane protocol stack. The UEs 112 and anng-eNB may be connected using the Uu interface using the LTE user planeand control plane protocol stack.

In the example mobile communications system of FIG. 1B, a 5G-CN isconnected to a RAN comprised of 4G LTE and/or 5G NR RATs. In otherexample mobile communications systems, a RAN based on the 5G NR RAT maybe connected to a 4G CN (e.g., EPC). For example, earlier releases of 5Gstandards may support a non-standalone mode of operation where a NRbased RAN is connected to the 4G EPC. In an example non-standalone mode,a UE may be connected to both a 5G NR gNB and a 4G LTE eNB (e.g., ang-eNB) and the control plane functionalities (such as initial access,paging and mobility) may be provided through the 4G LTE eNB. In astandalone of operation, the 5G NR gNB is connected to a 5G-CN and theuser plane and the control plane functionalities are provided by the 5GNR gNB.

FIG. 2A shows an example of the protocol stack for the user plan of anNR Uu interface in accordance with several of various embodiments of thepresent disclosure. The user plane protocol stack comprises fiveprotocol layers that terminate at the UE 200 and the gNB 210. The fiveprotocol layers, as shown in FIG. 2A, include physical (PHY) layerreferred to as PHY 201 at the UE 200 and PHY 211 at the gNB 210, mediumaccess control (MAC) layer referred to as MAC 202 at the UE 200 and MAC212 at the gNB 210, radio link control (RLC) layer referred to as RLC203 at the UE 200 and RLC 213 at the gNB 210, packet data convergenceprotocol (PDCP) layer referred to as PDCP 204 at the UE 200 and PDCP 214at the gNB 210, and service data application protocol (SDAP) layerreferred to as SDAP 205 at the UE 200 and SDAP 215 at the gNB 210. ThePHY layer, also known as layer 1 (L1), offers transport services tohigher layers. The other four layers of the protocol stack (MAC, RLC,PDCP and SDAP) are collectively known as layer 2 (L2).

FIG. 2B shows an example of the protocol stack for the control plan ofan NR Uu interface in accordance with several of various embodiments ofthe present disclosure. Some of the protocol layers (PHY, MAC, RLC andPDCP) are common between the user plane protocol stack shown in FIG. 2Aand the control plan protocol stack. The control plane protocol stackalso includes the RRC layer, referred to RRC 206 at the UE 200 and RRC216 at the gNB 210, that also terminates at the UE 200 and the gNB 210.In addition, the control plane protocol stack includes the NAS layerthat terminates at the UE 200 and the AMF 220. In FIG. 2B, the NAS layeris referred to as NAS 207 at the UE 200 and NAS 227 at the AMF 220.

FIG. 3 shows example functions and services offered to other layers by alayer in the NR user plane protocol stack of FIG. 2A in accordance withseveral of various embodiments of the present disclosure. For example,the SDAP layer of FIG. 3 (shown in FIG. 2A as SDAP 205 at the UE sideand SDAP 215 at the gNB side) may perform mapping and de-mapping of QoSflows to data radio bearers. The mapping and de-mapping may be based onQoS (e.g., delay, throughput, jitter, error rate, etc.) associated witha QoS flow. A QoS flow may be a QoS differentiation granularity for aPDU session which is a logical connection between a UE 200 and a datanetwork. A PDU session may contain one or more QoS flows. The functionsand services of the SDAP layer include mapping and de-mapping betweenone or more QoS flows and one or more data radio bearers. The SDAP layermay also mark the uplink and/or downlink packets with a QoS flow ID(QFI).

The PDCP layer of FIG. 3 (shown in FIG. 2A as PDCP 204 at the UE sideand PDCP 214 at the gNB side) may perform header compression anddecompression (e.g., using Robust Header Compression (ROHC) protocol) toreduce the protocol header overhead, ciphering and deciphering andintegrity protection and verification to enhance the security over theair interface, reordering and in-order delivery of packets anddiscarding of duplicate packets. A UE may be configured with one PDCPentity per bearer.

In an example scenario not shown in FIG. 3, a UE may be configured withdual connectivity and may connect to two different cell groups providedby two different base stations. For example, a base station of the twobase stations may be referred to as a master base station and a cellgroup provided by the master base station may be referred to as a mastercell group (MCG). The other base station of the two base stations may bereferred to as a secondary base station and the cell group provided bythe secondary base station may be referred to as a secondary cell group(SCG). A bearer may be configured for the UE as a split bearer that maybe handled by the two different cell groups. The PDCP layer may performrouting of packets corresponding to a split bearer to and/or from RLCchannels associated with the cell groups.

In an example scenario not shown in FIG. 3, a bearer of the UE may beconfigured (e.g., with control signaling) with PDCP packet duplication.A bearer configured with PDCP duplication may be mapped to a pluralityof RLC channels each corresponding to different one or more cells. ThePDCP layer may duplicate packets of the bearer configured with PDCPduplication and the duplicated packets may be mapped to the differentRLC channels. With PDCP packet duplication, the likelihood of correctreception of packets increases thereby enabling higher reliability.

The RLC layer of FIG. 3 (shown in FIG. 2A as RLC 203 at the UE side andRLC 213 at the gNB side) provides service to upper layers in the form ofRLC channels. The RLC layer may include three transmission modes:transparent mode (TM), Unacknowledged mode (UM) and Acknowledged mode(AM). The RLC layer may perform error correction through automaticrepeat request (ARQ) for the AM transmission mode, segmentation of RLCservice data units (SDUs) for the AM and UM transmission modes andre-segmentation of RLC SDUs for AM transmission mode, duplicatedetection for the AM transmission mode, RLC SDU discard for the AM andUM transmission modes, etc. The UE may be configured with one RLC entityper RLC channel.

The MAC layer of FIG. 3 (shown in FIG. 2A as MAC 202 at the UE side andMAC 212 at the gNB side) provides services to the RLC layer in form oflogical channels. The MAC layer may perform mapping between logicalchannels and transport channels, multiplexing/demultiplexing of MAC SDUsbelonging to one or more logical channels into/from transport blocks(TBs) delivered to/from the physical layer on transport channels,reporting of scheduling information, error correction through hybridautomatic repeat request (HARQ), priority handling between UEs by meansof dynamic scheduling, priority handling between logical channels of oneUE by means of logical channel prioritization and/or padding. In case ofcarrier aggregation, a MAC entity may comprise one HARQ entity per cell.A MAC entity may support multiple numerologies, transmission timings andcells. The control signaling may configure logical channels with mappingrestrictions. The mapping restrictions in logical channel prioritizationmay control the numerology(ies), cell(s), and/or transmissiontiming(s)/duration(s) that a logical channel may use.

The PHY layer of FIG. 3 (shown in FIG. 2A as PHY 201 at the UE side andPHY 211 at the gNB side) provides transport services to the MAC layer inform of transport channels. The physical layer may handlecoding/decoding, HARQ soft combining, rate matching of a coded transportchannel to physical channels, mapping of coded transport channels tophysical channels, modulation and demodulation of physical channels,frequency and time synchronization, radio characteristics measurementsand indication to higher layers, RF processing, and mapping to antennasand radio resources.

FIG. 4 shows example processing of packets at different protocol layersin accordance with several of various embodiments of the presentdisclosure. In this example, three Internet Protocol (IP) packets thatare processed by the different layers of the NR protocol stack. The termSDU shown in FIG. 4 is the data unit that is entered from/to a higherlayer. In contrast, a protocol data unit (PDU) is the data unit that isentered to/from a lower layer. The flow of packets in FIG. 4 is fordownlink. An uplink data flow through layers of the NR protocol stack issimilar to FIG. 4. In this example, the two leftmost IP packets aremapped by the SDAP layer (shown as SDAP 205 and SDAP 215 in FIG. 2A) toradio bearer 402 and the rightmost packet is mapped by the SDAP layer tothe radio bearer 404. The SDAP layer adds SDAP headers to the IP packetswhich are entered into the PDCP layer as PDCP SDUs. The PDCP layer isshown as PDCP 204 and PDCP 214 in FIG. 2A. The PDCP layer adds the PDCPheaders to the PDCP SDUs which are entered into the RLC layer as RLCSDUs. The RLC layer is shown as RLC 203 and RLC 213 in FIG. 2A. An RLCSDU may be segmented at the RLC layer. The RLC layer adds RLC headers tothe RLC SDUs after segmentation (if segmented) which are entered intothe MAC layer as MAC SDUs. The MAC layer adds the MAC headers to the MACSDUs and multiplexes one or more MAC SDUs to form a PHY SDU (alsoreferred to as a transport block (TB) or a MAC PDU).

In FIG. 4, the MAC SDUs are multiplexed to form a transport block. TheMAC layer may multiplex one or more MAC control elements (MAC CEs) withzero or more MAC SDUs to form a transport block. The MAC CEs may also bereferred to as MAC commands or MAC layer control signaling and may beused for in-band control signaling. The MAC CEs may be transmitted by abase station to a UE (e.g., downlink MAC CEs) or by a UE to a basestation (e.g., uplink MAC CEs). The MAC CEs may be used for transmissionof information useful by a gNB for scheduling (e.g., buffer statusreport (BSR) or power headroom report (PHR)), activation/deactivation ofone or more cells, activation/deactivation of configured radio resourcesfor or one or more processes, activation/deactivation of one or moreprocesses, indication of parameters used in one or more processes, etc.

FIG. 5A and FIG. 5B show example mapping between logical channels,transport channels and physical channels for downlink and uplink,respectively in accordance with several of various embodiments of thepresent disclosure. As discussed before, the MAC layer provides servicesto higher layer in the form of logical channels. A logical channel maybe classified as a control channel, if used for transmission of controland/or configuration information, or a traffic channel if used fortransmission of user data. Example logical channels in NR includeBroadcast Control Channel (BCCH) used for transmission of broadcastsystem control information, Paging Control Channel (PCCH) used forcarrying paging messages for wireless devices with unknown locations,Common Control Channel (CCCH) used for transmission of controlinformation between UEs and network and for UEs that have no RRCconnection with the network, Dedicated Control Channel (DCCH) which is apoint-to-point bi-directional channel for transmission of dedicatedcontrol information between a UE that has an RRC connection and thenetwork and Dedicated Traffic Channel (DTCH) which is point-to-pointchannel, dedicated to one UE, for the transfer of user information andmay exist in both uplink and downlink.

As discussed before, the PHY layer provides services to the MAC layerand higher layers in the form of transport channels. Example transportchannels in NR include Broadcast Channel (BCH) used for transmission ofpart of the BCCH referred to as master information block (MIB), DownlinkShared Channel (DL-SCH) used for transmission of data (e.g., from DTCHin downlink) and various control information (e.g., from DCCH and CCCHin downlink and part of the BCCH that is not mapped to the BCH), UplinkShared Channel (UL-SCH) used for transmission of uplink data (e.g., fromDTCH in uplink) and control information (e.g., from CCCH and DCCH inuplink) and Paging Channel (PCH) used for transmission of paginginformation from the PCCH. In addition, Random Access Channel (RACH) isa transport channel used for transmission of random access preambles.The RACH does not carry a transport block. Data on a transport channel(except RACH) may be organized in transport blocks, wherein One or moretransport blocks may be transmitted in a transmission time interval(TTI).

The PHY layer may map the transport channels to physical channels. Aphysical channel may correspond to time-frequency resources that areused for transmission of information from one or more transportchannels. In addition to mapping transport channels to physicalchannels, the physical layer may generate control information (e.g.,downlink control information (DCI) or uplink control information (UCI))that may be carried by the physical channels. Example DCI includescheduling information (e.g., downlink assignments and uplink grants),request for channel state information report, power control command,etc. Example UCI include HARQ feedback indicating correct or incorrectreception of downlink transport blocks, channel state informationreport, scheduling request, etc. Example physical channels in NR includea Physical Broadcast Channel (PBCH) for carrying information from theBCH, a Physical Downlink Shared Channel (PDSCH) for carrying informationform the PCH and the DL-SCH, a Physical Downlink Control Channel (PDCCH)for carrying DCI, a Physical Uplink Shared Channel (PUSCH) for carryinginformation from the UL-SCH and/or UCI, a Physical Uplink ControlChannel (PUCCH) for carrying UCI and Physical Random Access Channel(PRACH) for transmission of RACH (e.g., random access preamble).

The PHY layer may also generate physical signals that are not originatedfrom higher layers. As shown in FIG. 5A, example downlink physicalsignals include Demodulation Reference Signal (DM-RS), Phase TrackingReference Signal (PT-RS), Channel State Information Reference Signal(CSI-RS), Primary Synchronization Signal (PSS) and SecondarySynchronization Signal (SSS). As shown in FIG. 5B, example uplinkphysical signals include DM-RS, PT-RS and sounding reference signal(SRS).

As indicated earlier, some of the protocol layers (PHY, MAC, RLC andPDCP) of the control plane of an NR Uu interface, are common between theuser plane protocol stack (as shown in FIG. 2A) and the control planeprotocol stack (as shown in FIG. 2B). In addition to PHY, MAC, RLC andPDCP, the control plane protocol stack includes the RRC protocol layerand the NAS protocol layer.

The NAS layer, as shown in FIG. 2B, terminates at the UE 200 and the AMF220 entity of the 5G-C 130. The NAS layer is used for core networkrelated functions and signaling including registration, authentication,location update and session management. The NAS layer uses services fromthe AS of the Uu interface to transmit the NAS messages.

The RRC layer, as shown in FIG. 2B, operates between the UE 200 and thegNB 210 (more generally NG-RAN 120) and may provide services andfunctions such as broadcast of system information (SI) related to AS andNAS as well as paging initiated by the 5G-C 130 or NG-RAN 120. Inaddition, the RRC layer is responsible for establishment, maintenanceand release of an RRC connection between the UE 200 and the NG-RAN 120,carrier aggregation configuration (e.g., addition, modification andrelease), dual connectivity configuration (e.g., addition, modificationand release), security related functions, radio bearerconfiguration/maintenance and release, mobility management (e.g.,maintenance and context transfer), UE cell selection and reselection,inter-RAT mobility, QoS management functions, UE measurement reportingand control, radio link failure (RLF) detection and NAS messagetransfer. The RRC layer uses services from PHY, MAC, RLC and PDCP layersto transmit RRC messages using signaling radio bearers (SRBs). The SRBsare mapped to CCCH logical channel during connection establishment andto DCCH logical channel after connection establishment.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure. Data and/or control streams from MAC layer may beencoded/decoded to offer transport and control services over the radiotransmission link. For example, one or more (e.g., two as shown in FIG.6) transport blocks may be received from the MAC layer for transmissionvia a physical channel (e.g., a physical downlink shared channel or aphysical uplink shared channel). A cyclic redundancy check (CRC) may becalculated and attached to a transport block in the physical layer. TheCRC calculation may be based on one or more cyclic generatorpolynomials. The CRC may be used by the receiver for error detection.Following the transport block CRC attachment, a low-density parity check(LDPC) base graph selection may be performed. In example embodiments,two LDPC base graphs may be used wherein a first LDPC base graph may beoptimized for small transport blocks and a second LDPC base graph may beoptimized for comparatively larger transport blocks.

The transport block may be segmented into code blocks and code block CRCmay be calculated and attached to a code block. A code block may be LDPCcoded and the LDPC coded blocks may be individually rate matched. Thecode blocks may be concatenated to create one or more codewords. Thecontents of a codeword may be scrambled and modulated to generate ablock of complex-valued modulation symbols. The modulation symbols maybe mapped to a plurality of transmission layers (e.g., multiple-inputmultiple-output (MIMO) layers) and the transmission layers may besubject to transform precoding and/or precoding. The precodedcomplex-valued symbols may be mapped to radio resources (e.g., resourceelements). The signal generator block may create a baseband signal andup-convert the baseband signal to a carrier frequency for transmissionvia antenna ports. The signal generator block may employ mixers, filtersand/or other radio frequency (RF) components prior to transmission viathe antennas. The functions and blocks in FIG. 6 are illustrated asexamples and other mechanisms may be implemented in various embodiments.

FIG. 7 shows examples of RRC states and RRC state transitions at a UE inaccordance with several of various embodiments of the presentdisclosure. A UE may be in one of three RRC states: RRC_IDLE 702, RRCINACTIVE 704 and RRC_CONNECTED 706. In RRC_IDLE 702 state, no RRCcontext (e.g., parameters needed for communications between the UE andthe network) may be established for the UE in the RAN. In RRC_IDLE 702state, no data transfer between the UE and the network may take placeand uplink synchronization is not maintained. The wireless device maysleep most of the time and may wake up periodically to receive pagingmessages. The uplink transmission of the UE may be based on a randomaccess process and to enable transition to the RRC_CONNECTED 706 state.The mobility in RRC_IDLE 702 state is through a cell reselectionprocedure where the UE camps on a cell based on one or more criteriaincluding signal strength that is determined based on the UEmeasurements.

In RRC_CONNECTED 706 state, the RRC context is established and both theUE and the RAN have necessary parameters to enable communicationsbetween the UE and the network. In the RRC_CONNECTED 706 state, the UEis configured with an identity known as a Cell Radio Network TemporaryIdentifier (C-RNTI) that is used for signaling purposes (e.g., uplinkand downlink scheduling, etc.) between the UE and the RAN. The wirelessdevice mobility in the RRC_CONNECTED 706 state is managed by the RAN.The wireless device provides neighboring cells and/or current servingcell measurements to the network and the network may make hand overdecisions. Based on the wireless device measurements, the currentserving base station may send a handover request message to aneighboring base station and may send a handover command to the wirelessdevice to handover to a cell of the neighboring base station. Thetransition of the wireless device from the RRC_IDLE 702 state to the RRCCONNECTED 706 state or from the RRC_CONNECTED 706 state to the RRC_IDLE702 state may be based on connection establishment and connectionrelease procedures (shown collectively as connectionestablishment/release 710 in FIG. 7).

To enable a faster transition to the RRC_CONNECTED 706 state (e.g.,compared to transition from RRC_IDLE 702 state to RRC_CONNECTED 706state), an RRC_INACTIVE 704 state is used for an NR UE wherein, the RRCcontext is kept at the UE and the RAN. The transition from theRRC_INACTIVE 704 state to the RRC_CONNECTED 706 state is handled by RANwithout CN signaling. Similar to the RRC_IDLE 702 state, the mobility inRRC_INACTIVE 704 state is based on a cell reselection procedure withoutinvolvement from the network. The transition of the wireless device fromthe RRC_INACTIVE 704 state to the RRC_CONNECTED 706 state or from theRRC_CONNECTED 706 state to the RRC_INACTIVE 704 state may be based onconnection resume and connection inactivation procedures (showncollectively as connection resume/inactivation 712 in FIG. 7). Thetransition of the wireless device from the RRC_INACTIVE 704 state to theRRC_IDLE 702 state may be based on a connection release 714 procedure asshown in FIG. 7.

In NR, Orthogonal Frequency Division Multiplexing (OFDM), also calledcyclic prefix OFDM (CP-OFDM), is the baseline transmission scheme inboth downlink and uplink of NR and the Discrete Fourier Transform (DFT)spread OFDM (DFT-s-OFDM) is a complementary uplink transmission inaddition to the baseline OFDM scheme. OFDM is multi-carrier transmissionscheme wherein the transmission bandwidth may be composed of severalnarrowband sub-carriers. The subcarriers are modulated by the complexvalued OFDM modulation symbols resulting in an OFDM signal. The complexvalued OFDM modulation symbols are obtained by mapping, by a modulationmapper, the input data (e.g., binary digits) to different points of amodulation constellation diagram. The modulation constellation diagramdepends on the modulation scheme. NR may use different types ofmodulation schemes including Binary Phase Shift Keying (BPSK), π/2-BPSK,Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation(16QAM), 64QAM and 256QAM. Different and/or higher order modulationschemes (e.g., M-QAM in general) may be used. An OFDM signal with Nsubcarriers may be generated by processing N subcarriers in parallel forexample by using Inverse Fast Fourier Transform (IFFT) processing. TheOFDM receiver may use FFT processing to recover the transmitted OFDMmodulation symbols. The subcarrier spacing of subcarriers in an OFDMsignal is inversely proportional to an OFDM modulation symbol duration.For example, for a 15 KHz subcarrier spacing, duration of an OFDM signalis nearly 66.7 μs. To enhance the robustness of OFDM transmission intime dispersive channels, a cyclic prefix (CP) may be inserted at thebeginning of an OFDM symbol. For example, the last part of an OFDMsymbol may be copied and inserted at the beginning of an OFDM symbol.The CP insertion enhanced the OFDM transmission scheme by preservingsubcarrier orthogonality in time dispersive channels.

In NR, different numerologies may be used for OFDM transmission. Anumerology of OFDM transmission may indicate a subcarrier spacing and aCP duration for the OFDM transmission. For example, a subcarrier spacingin NR may generally be a multiple of 15 KHz and expressed as Δf=2^(μ).15 KHz (μ=0, 1, 2, . . . ). Example subcarrier spacings used in NRinclude 15 KHz (μ=0), 30 KHz (μ=1), 60 KHz (μ=2), 120 KHz (μ=3) and 240KHz (μ=4). As discussed before, a duration of OFDM symbol is inverselyproportional to the subcarrier spacing and therefor OFDM symbol durationmay depend on the numerology (e.g. the μ value).

FIG. 8 shows an example time domain transmission structure in NR whereinOFDM symbols are grouped into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure. A slot isa group of N_(symb) ^(slot) OFDM symbols, wherein the N_(symb) ^(slot)may have a constant value (e.g., 14). Since different numerologiesresults in different OFDM symbol durations, duration of a slot may alsodepend on the numerology and may be variable. A subframe may have aduration of 1 ms and may be composed of one or more slots, the number ofwhich may depend on the slot duration. The number of slots per subframeis therefore a function of μ and may generally expressed as N_(symb)^(subframe,μ) and the number of symbols per subframe may be expressed asN_(symb) ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). A framemay have a duration of 10 ms and may consist of 10 subframes. The numberof slots per frame may depend on the numerology and therefore may bevariable. The number of slots per frame may generally be expressed asN_(slot) ^(frame,μ).

An antenna port may be defined as a logical entity such that channelcharacteristics over which a symbol on the antenna port is conveyed maybe inferred from the channel characteristics over which another symbolon the same antenna port is conveyed. For example, for DM-RS associatedwith a PDSCH, the channel over which a PDSCH symbol on an antenna portis conveyed may be inferred from the channel over which a DM-RS symbolon the same antenna port is conveyed, for example, if the two symbolsare within the same resource as the scheduled PDSCH and/or in the sameslot and/or in the same precoding resource block group (PRG). Forexample, for DM-RS associated with a PDCCH, the channel over which aPDCCH symbol on an antenna port is conveyed may be inferred from thechannel over which a DM-RS symbol on the same antenna port is conveyedif, for example, the two symbols are within resources for which the UEmay assume the same precoding being used. For example, for DM-RSassociated with a PBCH, the channel over which a PBCH symbol on oneantenna port is conveyed may be inferred from the channel over which aDM-RS symbol on the same antenna port is conveyed if, for example, thetwo symbols are within a SS/PBCH block transmitted within the same slot,and with the same block index. The antenna port may be different from aphysical antenna. An antenna port may be associated with an antenna portnumber and different physical channels may correspond to differentranges of antenna port numbers.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure. Thenumber of subcarriers in a carrier bandwidth may be based on thenumerology of OFDM transmissions in the carrier. A resource element,corresponding to one symbol duration and one subcarrier, may be thesmallest physical resource in the time-frequency grid. A resourceelement (RE) for antenna port p and subcarrier spacing configuration μmay be uniquely identified by (k,l)_(p,μ)where k is the index of asubcarrier in the frequency domain and 1 may refer to the symbolposition in the time domain relative to some reference point. A resourceblock may be defined as N_(SC) ^(RB)=12 subcarriers. Since subcarrierspacing depends on the numerology of OFDM transmission, the frequencydomain span of a resource block may be variable and may depend on thenumerology. For example, for a subcarrier spacing of 15 KHz (e.g., μ=0),a resource block may be 180 KHz and for a subcarrier spacing of 30 KHz(e.g., μ=1), a resource block may be 360 KHz.

With large carrier bandwidths defined in NR and due to limitedcapabilities for some UEs (e.g., due to hardware limitations), a UE maynot support an entire carrier bandwidth. Receiving on the full carrierbandwidth may imply high energy consumption. For example, transmittingdownlink control channels on the full downlink carrier bandwidth mayresult in high power consumption for wide carrier bandwidths. NR may usea bandwidth adaptation procedure to dynamically adapt the transmit andreceive bandwidths. The transmit and receive bandwidth of a UE on a cellmay be smaller than the bandwidth of the cell and may be adjusted. Forexample, the width of the transmit and/or receive bandwidth may change(e.g. shrink during period of low activity to save power); the locationof the transmit and/or receive bandwidth may move in the frequencydomain (e.g. to increase scheduling flexibility); and the subcarrierspacing of the transmit or receive bandwidth may change (e.g. to allowdifferent services). A subset of the cell bandwidth may be referred toas a Bandwidth Part (BWP) and bandwidth adaptation may be achieved byconfiguring the UE with one or more BWPs. The base station may configurea UE with a set of downlink BWPs and a set of uplink BWPs. A BWP may becharacterized by a numerology (e.g., subcarrier spacing and cyclicprefix) and a set of consecutive resource blocks in the numerology ofthe BWP. One or more first BWPs of the one or more BWPs of the cell maybe active at a time. An active BWP may be an active downlink BWP or anactive uplink BWP.

FIG. 10 shows an example of bandwidth part adaptation and switching. Inthis example, three BWPs (BWP₁ 1004, BWP₂ 1006 and BWP₃ 1008) areconfigured for a UE on a carrier bandwidth. The BWP₁ is configured witha bandwidth of 40 MHz and a numerology with subcarrier spacing of 15KHz, the BWP₂ is configured with a bandwidth of 10 MHz and a numerologywith subcarrier spacing of 15 KHz and the BWP₃ is configured with abandwidth of 20 MHz and a subcarrier spacing of 60 KHz. The wirelessdevice may switch from a first BWP (e.g., BWP₁) to a second BWP (e.g.,BWP₂). An active BWP of the cell may change from the first BWP to thesecond BWP in response to the BWP switching.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10) may be based on acommand from the base station. The command may be a DCI comprisingscheduling information for the UE in the second BWP. In case of uplinkBWP switching, the first BWP and the second BWP may be uplink BWPs andthe scheduling information may be an uplink grant for uplinktransmission via the second BWP. In case of downlink BWP switching, thefirst BWP and the second BWP may be downlink BWPs and the schedulinginformation may be a downlink assignment for downlink reception via thesecond BWP.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10) may be based on anexpiry of a timer. The base station may configure a wireless device witha BWP inactivity timer and the wireless device may switch to a defaultBWP (e.g., default downlink BWP) based on the expiry of the BWPinactivity timer. The expiry of the BWP inactivity timer may be anindication of low activity on the current active downlink BWP. The basestation may configure the wireless device with the default downlink BWP.If the base station does not configure the wireless device with thedefault BWP, the default BWP may be an initial downlink BWP. The initialactive BWP may be the BWP that the wireless device receives schedulinginformation for remaining system information upon transition to anRRC_CONNECTED state.

A wireless device may monitor a downlink control channel of a downlinkBWP. For example, the UE may monitor a set of PDCCH candidates inconfigured monitoring occasions in one or more configured COntrolREsource SETs (CORESETs) according to the corresponding search spaceconfigurations. A search space configuration may define how/where tosearch for PDCCH candidates. For example, the search space configurationparameters may comprise a monitoring periodicity and offset parameterindicating the slots for monitoring the PDCCH candidates. The searchspace configuration parameters may further comprise a parameterindicating a first symbol with a slot within the slots determined formonitoring PDCCH candidates. A search space may be associated with oneor more CORESETs and the search space configuration may indicate one ormore identifiers of the one or more CORESETs. The search spaceconfiguration parameters may further indicate that whether the searchspace is a common search space or a UE-specific search space. A commonsearch space may be monitored by a plurality of wireless devices and aUE-specific search space may be dedicated to a specific UE.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure. With carrier aggregation, multiple NR component carriers(CCs) may be aggregated. Downlink transmissions to a wireless device maytake place simultaneously on the aggregated downlink CCs resulting inhigher downlink data rates. Uplink transmissions from a wireless devicemay take place simultaneously on the aggregated uplink CCs resulting inhigher uplink data rates. The component carriers in carrier aggregationmay be on the same frequency band (e.g., intra-band carrier aggregation)or on different frequency bands (e.g., inter-band carrier aggregation).The component carriers may also be contiguous or non-contiguous. Thisresults in three possible carrier aggregation scenarios, intra-bandcontiguous CA 1102, intra-band non-contiguous CA 1104 and inter-band CA1106 as shown in FIG. 11A. Depending on the UE capability for carrieraggregation, a UE may transmit and/or receive on multiple carriers orfor a UE that is not capable of carrier aggregation, the UE may transmitand/or receive on one component carrier at a time. In this disclosure,the carrier aggregation is described using the term cell and a carrieraggregation capable UE may transmit and/or receive via multiple cells.

In carrier aggregation, a UE may be configured with multiple cells. Acell of the multiple cells configured for the UE may be referred to as aPrimary Cell (PCell). The PCell may be the first cell that the UE isinitially connected to. One or more other cells configured for the UEmay be referred to as Secondary Cells (SCells). The base station mayconfigure a UE with multiple SCells. The configured SCells may bedeactivated upon configuration and the base station may dynamicallyactivate or deactivate one or more of the configured SCells based ontraffic and/or channel conditions. The base station may activate ordeactivate configured SCells using a SCell Activation/Deactivation MACCE. The SCell Activation/Deactivation MAC CE may comprise a bitmap,wherein each bit in the bitmap may correspond to a SCell and the valueof the bit indicates an activation status or deactivation status of theSCell.

An SCell may also be deactivated in response to expiry of a SCelldeactivation timer of the SCell. The expiry of an SCell deactivationtimer of an SCell may be an indication of low activity (e.g., lowtransmission or reception activity) on the SCell. The base station mayconfigure the SCell with an SCell deactivation timer. The base stationmay not configure an SCell deactivation timer for an SCell that isconfigured with PUCCH (also referred to as a PUCCH SCell). Theconfiguration of the SCell deactivation timer may be per configuredSCell and different SCells may be configured with different SCelldeactivation timer values. The SCell deactivation timer may be restartedbased on one or more criteria including reception of downlink controlinformation on the SCell indicating uplink grant or downlink assignmentfor the SCell or reception of downlink control information on ascheduling cell indicating uplink grant or downlink assignment for theSCell or transmission of a MAC PDU based on a configured uplink grant orreception of a configured downlink assignment.

A PCell for a UE may be an SCell for another UE and a SCell for a UE maybe PCell for another UE. The configuration of PCell may be UE-specific.One or more SCells of the multiple SCells configured for a UE may beconfigured as downlink-only SCells, e.g., may only be used for downlinkreception and may not be used for uplink transmission. In case ofself-scheduling, the base station may transmit signaling for uplinkgrants and/or downlink assignments on the same cell that thecorresponding uplink or downlink transmission takes place. In case ofcross-carrier scheduling, the base station may transmit signaling foruplink grants and/or downlink assignments on a cell different from thecell that the corresponding uplink or downlink transmission takes place.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure. A basestation may configure a UE with multiple PUCCH groups wherein a PUCCHgroup comprises one or more cells. For example, as shown in FIG. 11B,the base station may configure a UE with a primary PUCCH group 1114 anda secondary PUCCH group 1116. The primary PUCCH group may comprise thePCell 1110 and one or more first SCells. First UCI corresponding to thePCell and the one or more first SCells of the primary PUCCH group may betransmitted by the PUCCH of the PCell. The first UCI may be, forexample, HARQ feedback for downlink transmissions via downlink CCs ofthe PCell and the one or more first SCells. The secondary PUCCH groupmay comprise a PUCCH SCell and one or more second SCells. Second UCIcorresponding to the PUCCH SCell and the one or more second SCells ofthe secondary PUCCH group may be transmitted by the PUCCH of the PUCCHSCell. The second UCI may be, for example, HARQ feedback for downlinktransmissions via downlink CCs of the PUCCH SCell and the one or moresecond SCells.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure. FIG. 12A shows an example of four step contention-basedrandom access (CBRA) procedure. The four-step CBRA procedure includesexchanging four messages between a UE and a base station. Msg1 may befor transmission (or retransmission) of a random access preamble by thewireless device to the base station. Msg2 may be the random accessresponse (RAR) by the base station to the wireless device. Msg3 is thescheduled transmission based on an uplink grant indicated in Msg2 andMsg4 may be for contention resolution.

The base station may transmit one or more RRC messages comprisingconfiguration parameters of the random access parameters. The randomaccess parameters may indicate radio resources (e.g., time-frequencyresources) for transmission of the random access preamble (e.g., Msg1),configuration index, one or more parameters for determining the power ofthe random access preamble (e.g., a power ramping parameter, a preamblereceived target power, etc.), a parameter indicating maximum number ofpreamble transmission, RAR window for monitoring RAR, cell-specificrandom access parameters and UE specific random access parameters. TheUE-specific random access parameters may indicate one or more PRACHoccasions for random access preamble (e.g., Msg1) transmissions. Therandom access parameters may indicate association between the PRACHoccasions and one or more reference signals (e.g., SSB or CSI-RS). Therandom access parameters may further indicate association between therandom access preambles and one or more reference signals (e.g., SBB orCSI-RS). The UE may use one or more reference signals (e.g., SSB(s) orCSI-RS(s)) and may determine a random access preamble to use for Msg1transmission based on the association between the random accesspreambles and the one or more reference signals. The UE may use one ormore reference signals (e.g., SSB(s) or CSI-RS(s)) and may determine thePRACH occasion to use for Msg1 transmission based on the associationbetween the PRACH occasions and the reference signals. The UE mayperform a retransmission of the random access preamble if no response isreceived with the RAR window following the transmission of the preamble.UE may use a higher transmission power for retransmission of thepreamble. UE may determine the higher transmission power of the preamblebased on the power ramping parameter.

Msg2 is for transmission of RAR by the base station. Msg2 may comprise aplurality of RARs corresponding to a plurality of random accesspreambles transmitted by a plurality of UEs. Msg2 may be associated witha random access temporary radio identifier (RA-RNTI) and may be receivedin a common search space of the UE. The RA-RNTI may be based on thePRACH occasion (e.g., time and frequency resources of a PRACH) in whicha random access preamble is transmitted. RAR may comprise a timingadvance command for uplink timing adjustment at the UE, an uplink grantfor transmission of Msg3 and a temporary C-RNTI. In response to thesuccessful reception of Msg2, the UE may transmit the Msg3. Msg3 andMsg4 may enable contention resolution in case of CBRA. In a CBRA, aplurality of UEs may transmit the same random access preamble and mayconsider the same RAR as being corresponding to them. UE may include adevice identifier in Msg3 (e.g., a C-RNTI, temporary C-RNTI or other UEidentity). Base station may transmit the Msg4 with a PDSCH and UE mayassume that the contention resolution is successful in response to thePDSCH used for transmission of Msg4 being associated with the UEidentifier included in Msg3.

FIG. 12B shows an example of a contention-free random access (CFRA)process. Msg 1 (random access preamble) and Msg 2 (random accessresponse) in FIG. 12B for CFRA may be analogous to Msg 1 and Msg 2 inFIG. 12A for CBRA. In an example, the CFRA procedure may be initiated inresponse to a PDCCH order from a base station. The PDCCH order forinitiating the CFRA procedure by the wireless device may be based on aDCI having a first format (e.g., format 1_0). The DCI for the PDCCHorder may comprise a random access preamble index, an UL/SUL indicatorindicating an uplink carrier of a cell (e.g., normal uplink carrier orsupplementary uplink carrier) for transmission of the random accesspreamble, a SS/PBCH index indicating the SS/PBCH that may be used todetermine a RACH occasion for PRACH transmission, a PRACH mask indexindicating the RACH occasion associated with the SS/PBCH indicated bythe SS/PBCH index for PRACH transmission, etc. In an example, the CFRAprocess may be started in response to a beam failure recovery process.The wireless device may start the CFRA for the beam failure recoverywithout a command (e.g., PDCCH order) from the base station and by usingthe wireless device dedicated resources.

FIG. 12C shows an example of a two-step random access process comprisingtwo messages exchanged between a wireless device and a base station. MsgA may be transmitted by the wireless device to the base station and maycomprise one or more transmissions of a preamble and/or one or moretransmissions of a transport block. The transport block in Msg A and Msg3 in FIG. 12A may have similar and/or equivalent contents. The transportblock of Msg A may comprise data and control information (e.g., SR, HARQfeedback, etc.). In response to the transmission of Msg A, the wirelessdevice may receive Msg B from the base station. Msg B in FIG. 12C andMsg 2 (e.g., RAR) illustrated in FIGS. 12A and 12B may have similarand/or equivalent content.

The base station may periodically transmit synchronization signals(SSs), e.g., primary SS (PSS) and secondary SS (SSS) along with PBCH oneach NR cell. The PSS/SSS together with PBCH is jointly referred to as aSS/PBCH block. The SS/PBCH block enables a wireless device to find acell when entering to the mobile communications network or find newcells when moving within the network. The SS/PBCH block spans four OFDMsymbols in time domain. The PSS is transmitted in the first symbol andoccupies 127 subcarriers in frequency domain. The SSS is transmitted inthe third OFDM symbol and occupies the same 127 subcarriers as the PSS.The are eight and nine empty subcarriers on each side of the SSS. ThePBCH is transmitted on the second OFDM symbol occupying 240 subcarriers,the third OFDM symbol occupying 48 subcarriers on each side of the SSS,and on the fourth OFDM symbol occupying 240 subcarriers. Some of thePBCH resources indicated above may be used for transmission of thedemodulation reference signal (DMRS) for coherent demodulation of thePBCH. The SS/PBCH block is transmitted periodically with a periodranging from 5 ms to 160 ms. For initial cell search or for cell searchduring inactive/idle state, a wireless device may assume that that theSS/PBCH block is repeated at least every 20 ms.

In NR, transmissions using of antenna arrays, with many antennaelements, and beamforming plays an important role specially in higherfrequency bands. Beamforming enables higher capacity by increasing thesignal strength (e.g., by focusing the signal energy in a specificdirection) and by lowering the amount interference received at thewireless devices. The beamforming techniques may generally be divided toanalog beamforming and digital beamforming techniques. With digitalbeamforming, signal processing for beamforming is carried out in thedigital domain before digital-to-analog conversion and detailed controlof both amplitude and phase of different antenna elements may bepossible. With analog beamforming, the signal processing for beamformingis carried out in the analog domain and after the digital to analogconversion. The beamformed transmissions may be in one direction at atime. For example, the wireless devices that are in different directionsrelative to the base station may receive their downlink transmissions atdifferent times. For analog receiver-side beamforming, the receiver mayfocus its receiver beam in one direction at a time.

In NR, the base station may use beam sweeping for transmission ofSS/PBCH blocks. The SS/PBCH blocks may be transmitted in different beamsusing time multiplexing. The set of SS/PBCH blocks that are transmittedin one beam sweep may be referred to as a SS/PBCH block set. The periodof PBCH/SSB block transmission may be a time duration between a SS/PBCHblock transmission in a beam and the next SS/PBCH block transmission inthe same beam. The period of SS/PBCH block is, therefore, also theperiod of the SS/PBCH block set.

FIG. 13A shows example time and frequency structure of SS/PBCH blocksand their associations with beams in accordance with several of variousembodiments of the present disclosure. In this example, a SS/PBCH block(also referred to as SSB) set comprise L SSBs wherein an SSB in the SSBset is associated with (e.g., transmitted in) one of L beams of a cell.The transmission of SBBs of an SSB set may be confined within a 5 msinterval, either in a first half-frame or a second half-frame of a 10 msframe. The number of SSBs in an SSB set may depend on the frequency bandof operation. For example, the number of SSBs in a SSB set may be up tofour SSBs in frequency bands below 3 GHz enabling beam sweeping of up tofour beams, up to eight SSBs in frequency bands between 3 GHz and 6 GHzenabling beam sweeping of up to eight beams, and up to sixty four SSBsin higher frequency bands enabling beam sweeping of up to sixty fourbeams. The SSs of an SSB may depend on a physical cell identity (PCI) ofthe cell and may be independent of which beam of the cell is used fortransmission of the SSB. The PBCH of an SSB may indicate a time indexparameter and the wireless device may determine the relative position ofthe SSB within the SSB set using the time index parameter. The wirelessdevice may use the relative position of the SSB within an SSB set fordetermining the frame timing and/or determining RACH occasions for arandom access process.

A wireless device entering the mobile communications network may firstsearch for the PSS. After detecting the PSS, the wireless device maydetermine the synchronization up to the periodicity of the PSS. Bydetecting the PSS, the wireless device may determine the transmissiontiming of the SSS. The wireless device may determine the PCI of the cellafter detecting the SSS. The PBCH of a SS/PBCH block is a downlinkphysical channel that carries the MIB. The MIB may be used by thewireless device to obtain remaining system information (RMSI) that isbroadcast by the network. The RMSI may include System Information Block1 (SIB1) that contains information required for the wireless device toaccess the cell.

As discussed earlier, the wireless device may determine a time indexparameter from the SSB. The PBCH comprises a half-frame parameterindicating whether the SSB is in the first 5 ms half or the second 5 mshalf of a 10 ms frame. The wireless device may determine the frameboundary using the time index parameter and the half-frame parameter. Inaddition, the PBCH may comprise a parameter indicating the system framenumber (SFN) of the cell.

The base station may transmit CSI-RS and a UE may measure the CSI-RS toobtain channel state information (CSI). The base station may configurethe CSI-RS in a UE-specific manner. In some scenarios, same set ofCSI-RS resources may be configured for multiple UEs and one or moreresource elements of a CSI-RS resource may be shared among multiple UEs.A CSI-RS resource may be configured such that it does not collide with aCORESET configured for the wireless device and/or with a DMRS of a PDSCHscheduled for the wireless device and/or transmitted SSBs. The UE maymeasure one or more CSI-RSs configured for the UE and may generate a CSIreport based on the CSI-RS measurements and may transmit the CSI reportto the base station for scheduling, link adaptation and/or otherpurposes.

NR supports flexible CSI-RS configurations. A CSI-RS resource may beconfigured with single or multiple antenna ports and with configurabledensity. Based on the number of configured antenna ports, a CSI-RSresource may span different number of OFDM symbols (e.g., 1, 2, and 4symbols). The CSI-RS may be configured for a downlink BWP and may usethe numerology of the downlink BWP. The CSI-RS may be configured tocover the full bandwidth of the downlink BWP or a portion of thedownlink BWP. In some case, the CSI-RS may be repeated in every resourceblock of the CSI-RS bandwidth, referred to as CSI-RS with density equalto one. In some cases, the CSI-RS may be configured to be repeated inevery other resource block of the CSI-RS bandwidth. CSI-RS may benon-zero power (NZP) CSI-RS or zero-power (ZP) CSI-RS.

The base station may configure a wireless device with one or more setsof NZP CSI-RS resources. The base station may configure the wirelessdevice with a NZP CSI-RS resource set using an RRC information element(IE) NZP-CSI-RS-ResourceSet indicating a NZP CSI-RS resource setidentifier (ID) and parameters specific to the NZP CSI-RS resource set.An NZP CSI-RS resource set may comprise one or more CSI-RS resources. AnNZP CSI-RS resource set may be configured as part of the CSI measurementconfiguration.

The CSI-RS may be configured for periodic, semi-persistent or aperiodictransmission. In case of the periodic and semi-persistent CSI-RSconfigurations, the wireless device may be configured with a CSIresource periodicity and offset parameter that indicate a periodicityand corresponding offset in terms of number of slots. The wirelessdevice may determine the slots that the CSI-RSs are transmitted. Forsemi-persistent CSI-RS, the CSI-RS resources for CSI-RS transmissionsmay be activated and deactivated by using a semi-persistent (SP) CSI-CSIResource Set Activation/Deactivation MAC CE. In response to receiving aMAC CE indicating activation of semi-persistent CSI-RS resources, thewireless device may assume that the CSI-RS transmissions will continueuntil the CSI-RS resources for CSI-RS transmissions are activated.

As discussed before, CSI-RS may be configured for a wireless device asNZP CSI-RS or ZP CSI-RS. The configuration of the ZP CSI-RS may besimilar to the NZP CSI-RS with the difference that the wireless devicemay not carry out measurements for the ZP CSI-RS. By configuring ZPCSI-RS, the wireless device may assume that a scheduled PDSCH thatincludes resource elements from the ZP CSI-RS is rate matched aroundthose ZP CSI-RS resources. For example, a ZP CSI-RS resource configuredfor a wireless device may be an NZP CSI-RS resource for another wirelessdevice. For example, by configuring ZP CSI-RS resources for the wirelessdevice, the base station may indicate to the wireless device that thePDSCH scheduled for the wireless device is rate matched around the ZPCSI-RS resources.

A base station may configure a wireless device with channel stateinformation interference measurement (CSI-IM) resources. Similar to theCSI-RS configuration, configuration of locations and density of CSI-IMresources may be flexible. The CSI-IM resources may be periodic(configured with a periodicity), semi-persistent (configured with aperiodicity and activated and deactivated by MAC CE) or aperiodic(triggered by a DCI).

Tracking reference signals (TRSs) may be configured for a wirelessdevice as a set of sparse reference signals to assist the wireless intime and frequency tracking and compensating time and frequencyvariations in its local oscillator. The wireless device may further usethe TRSs for estimating channel characteristics such as delay spread ordoppler frequency. The base station may use a CSI-RS configuration forconfiguring TRS for the wireless device. The TRS may be configured as aresource set comprising multiple periodic NZP CSI-RS resources.

A base station may configure a UE and the UE may transmit soundingreference signals (SRSs) to enable uplink channel sounding/estimation atthe base station. The SRS may support up to four antenna ports and maybe designed with low cubic metric enabling efficient operation of thewireless device amplifier. The SRS may span one or more (e.g., one, twoor four) consecutive OFDM symbols in time domain and may be locatedwithin the last n (e.g., six) symbols of a slot. In the frequencydomain, the SRS may have a structure that is referred to as a combstructure and may be transmitted on every Nth subcarrier. Different SRStransmissions from different wireless devices may have different combstructures and may be multiplexed in frequency domain.

A base station may configure a wireless device with one or more SRSresource sets and an SRS resource set may comprise one or more SRSresources. The SRS resources in an SRS resources set may be configuredfor periodic, semi-persistent or aperiodic transmission. The periodicSRS and the semi-persistent SRS resources may be configured withperiodicity and offset parameters. The Semi-persistent SRS resources ofa configured semi-persistent SRS resource set may be activated ordeactivated by a semi-persistent (SP) SRS Activation/Deactivation MACCE. The set of SRS resources included in an aperiodic SRS resource setmay be activated by a DCI. A value of a field (e.g., an SRS requestfield) in the DCI may indicate activation of resources in an aperiodicSRS resource set from a plurality of SRS resource sets configured forthe wireless device.

An antenna port may be associated with one or more reference signals.The receiver may assume that the one or more reference signals,associated with the antenna port, may be used for estimating channelcorresponding to the antenna port. The reference signals may be used toderive channel state information related to the antenna port. Twoantenna ports may be referred to as quasi co-located if characteristics(e.g., large-scale properties) of the channel over which a symbol isconveyed on one antenna port may be inferred from the channel over whicha symbol is conveyed from another antenna port. For example, a UE mayassume that radio channels corresponding to two different antenna portshave the same large-scale properties if the antenna ports are specifiedas quasi co-located. In some cases, the UE may assume that two antennaports are quasi co-located based on signaling received from the basestation. Spatial quasi-colocation (QCL) between two signals may be, forexample, due to the two signals being transmitted from the same locationand in the same beam. If a receive beam is good for a signal in a groupof signals that are spatially quasi co-located, it may be assumed alsobe good for the other signals in the group of signals.

The CSI-RS in the downlink and the SRS in uplink may serve asquasi-location (QCL) reference for other physical downlink channels andphysical uplink channels, respectively. For example, a downlink physicalchannel (e.g., PDSCH or PDCCH) may be spatially quasi co-located with adownlink reference signal (e.g., CSI-RS or SSB). The wireless device maydetermine a receive beam based on measurement on the downlink referencesignal and may assume that the determined received beam is also good forreception of the physical channels (e.g., PDSCH or PDCCH) that arespatially quasi co-located with the downlink reference signal.Similarly, an uplink physical channel (e.g., PUSCH or PUCCH) may bespatially quasi co-located with an uplink reference signal (e.g., SRS).The base station may determine a receive beam based on measurement onthe uplink reference signal and may assume that the determined receivedbeam is also good for reception of the physical channels (e.g., PUSCH orPUCCH) that are spatially quasi co-located with the uplink referencesignal.

The Demodulation Reference Signals (DM-RSs) enables channel estimationfor coherent demodulation of downlink physical channels (e.g., PDSCH,PDCCH and PBH) and uplink physical channels (e.g., PUSCH and PUCCH). TheDM-RS may be located early in the transmission (e.g., front-loadedDM-RS) and may enable the receiver to obtain the channel estimate earlyand reduce the latency. The time-domain structure of the DM-RS (e.g.,symbols wherein the DM-RS are located in a slot) may be based ondifferent mapping types.

The Phase Tracking Reference Signals (PT-RSs) enables tracking andcompensation of phase variations across the transmission duration. Thephase variations may be, for example, due to oscillator phase noise. Theoscillator phase noise may become more sever in higher frequencies(e.g., mmWave frequency bands). The base station may configure the PT-RSfor uplink and/or downlink. The PT-RS configuration parameters mayindicate frequency and time density of PT-RS, maximum number of ports(e.g., uplink ports), resource element offset, configuration of uplinkPT-RS without transform precoder (e.g., CP-OFDM) or with transformprecoder (e.g., DFT-s-OFDM), etc. The subcarrier number and/or resourceblocks used for PT-RS transmission may be based on the C-RNTI of thewireless device to reduce risk of collisions between PT-RSs of wirelessdevices scheduled on overlapping frequency domain resources.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure. A beam of the L beams shown in FIG. 13B maybe associated with a corresponding CSI-RS resource. The base station maytransmit the CSI-RSs using the configured CSI-RS resources and a UE maymeasure the CSI-RSs (e.g., received signal received power (RSRP) of theCSI-RSs) and report the CSI-RS measurements to the base station based ona reporting configuration. For example, the base station may determineone or more transmission configuration indication (TCI) states and mayindicate the one or more TCI states to the UE (e.g., using RRCsignaling, a MAC CE and/or a DCI). Based on the one or more TCI statesindicated to the UE, the UE may determine a downlink receive beam andreceive downlink transmissions using the receive beam. In case of a beamcorrespondence, the UE may determine a spatial domain filter of atransmit beam based on spatial domain filter of a corresponding receivebeam. Otherwise, the UE may perform an uplink beam selection procedureto determine the spatial domain filter of the transmit beam. The UE maytransmit one or more SRSs using the SRS resources configured for the UEand the base station may measure the SRSs and determine/select thetransmit beam for the UE based the SRS measurements. The base stationmay indicate the selected beam to the UE. The CSI-RS resources shown inFIG. 13B may be for one UE. The base station may configure differentCSI-RS resources associated with a given beam for different UEs by usingfrequency division multiplexing.

A base station and a wireless device may perform beam managementprocedures to establish beam pairs (e.g., transmit and receive beams)that jointly provide good connectivity. For example, in the downlinkdirection, the UE may perform measurements for a beam pair and estimatechannel quality for a transmit beam by the base station (or atransmission reception point (TRP) more generally) and the receive beamby the UE. The UE may transmit a report indicating beam pair qualityparameters. The report may comprise one or more parameters indicatingone or more beams (e.g., a beam index, an identifier of reference signalassociated with a beam, etc.), one or more measurement parameters (e.g.,RSRP), a precoding matrix indicator (PMI), a channel quality indicator(CQI), and/or a rank indicator (RI).

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processes(referred to as P1, P2 and P3, respectively) in accordance with severalof various embodiments of the present disclosure. The P1 process shownin FIG. 14A may enable, based on UE measurements, selection of a basestation (or TRP more generally) transmit beam and/or a wireless devicereceive beam. The TRP may perform a beam sweeping procedure where theTRP may sequentially transmit reference signals (e.g., SSB and/orCSI-RS) on a set of beams and the UE may select a beam from the set ofbeams and may report the selected beam to the TRP. The P2 procedure asshown in FIG. 14B may be a beam refinement procedure. The selection ofthe TRP transmit beam and the UE receive beam may be regularlyreevaluated due to movements and/or rotations of the UE or movement ofother objects. In an example, the base station may perform the beamsweeping procedure over a smaller set of beams and the UE may select thebest beam over the smaller set. In an example, the beam shape may benarrower compared to beam selected based on the P1 procedure. Using theP3 procedure as shown in FIG. 14C, the TRP may fix its transmit beam andthe UE may refine its receive beam.

A wireless device may receive one or more messages from a base station.The one or more messages may comprise one or more RRC messages. The oneor more messages may comprise configuration parameters of a plurality ofcells for the wireless device. The plurality of cells may comprise aprimary cell and one or more secondary cells. For example, the pluralityof cells may be provided by a base station and the wireless device maycommunicate with the base station using the plurality of cells. Forexample, the plurality of cells may be provided by multiple base station(e.g., in case of dual and/or multi-connectivity). The wireless devicemay communicate with a first base station, of the multiple basestations, using one or more first cells of the plurality of cells. Thewireless device may communicate with a second base station of themultiple base stations using one or more second cells of the pluralityof cells.

The one or more messages may comprise configuration parameters used forprocesses in physical, MAC, RLC, PCDP, SDAP, and/or RRC layers of thewireless device. For example, the configuration parameters may includevalues of timers used in physical, MAC, RLC, PCDP, SDAP, and/or RRClayers. For example, the configuration parameters may include parametersfor configurating different channels (e.g., physical layer channel,logical channels, RLC channels, etc.) and/or signals (e.g., CSI-RS, SRS,etc.).

Upon starting a timer, the timer may start running until the timer isstopped or until the timer expires. A timer may be restarted if it isrunning. A timer may be started if it is not running (e.g., after thetimer is stopped or after the timer expires). A timer may be configuredwith or may be associated with a value (e.g., an initial value). Thetimer may be started or restarted with the value of the timer. The valueof the timer may indicate a time duration that the timer may be runningupon being started or restarted and until the timer expires. Theduration of a timer may not be updated until the timer is stopped orexpires (e.g., due to BWP switching). This specification may disclose aprocess that includes one or more timers. The one or more timers may beimplemented in multiple ways. For example, a timer may be used by thewireless device and/or base station to determine a time window [t1, t2],wherein the timer is started at time t1 and expires at time t2 and thewireless device and/or the base station may be interested in and/ormonitor the time window [t1, t2], for example to receive a specificsignaling. Other examples of implementation of a timer may be provided.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure. The wirelessdevice 1502 may communicate with the base station 1542 over the airinterface 1532. The wireless device 1502 may include a plurality ofantennas. The base station 1542 may include a plurality of antennas. Theplurality of antennas at the wireless device 1502 and/or the basestation 1542 enables different types of multiple antenna techniques suchas beamforming, single-user and/or multi-user MIMO, etc.

The wireless device 1502 and the base station 1542 may have one or moreof a plurality of modules/blocks, for example RF front end (e.g., RFfront end 1530 at the wireless device 1502 and RF front end 1570 at thebase station 1542), Data Processing System (e.g., Data Processing System1524 at the wireless device 1502 and Data Processing System 1564 at thebase station 1542), Memory (e.g., Memory 1512 at the wireless device1502 and Memory 1542 at the base station 1542). Additionally, thewireless device 1502 and the base station 1542 may have othermodules/blocks such as GPS (e.g., GPS 1514 at the wireless device 1502and GPS 1554 at the base station 1542).

An RF front end module/block may include circuitry between antennas anda Data Processing System for proper conversion of signals between thesetwo modules/blocks. An RF front end may include one or more filters(e.g., Filter(s) 1526 at RF front end 1530 or Filter(s) 1566 at the RFfront end 1570), one or more amplifiers (e.g., Amplifier(s) 1528 at theRF front end 1530 and Amplifier(s) 1568 at the RF front end 1570). TheAmplifier(s) may comprise power amplifier(s) for transmission andlow-noise amplifier(s) (LNA(s)) for reception.

The Data Processing System 1524 and the Data Processing System 1564 mayprocess the data to be transmitted or the received signals byimplementing functions at different layers of the protocol stack such asPHY, MAC, RLC, etc. Example PHY layer functions that may be implementedby the Data Processing System 1524 and/or 1564 may include forward errorcorrection, interleaving, rate matching, modulation, precoding, resourcemapping, MIMO processing, etc. Similarly, one or more functions of theMAC layer, RLC layer and/or other layers may be implemented by the DataProcessing System 1524 and/or the Data Processing System 1564. One ormore processes described in the present disclosure may be implemented bythe Data Processing System 1524 and/or the Data Processing System 1564.A Data Processing System may include an RF module (RF module 1516 at theData Processing System 1524 and RF module 1556 at the Data ProcessingSystem 1564) and/or a TX/RX processor (e.g., TX/RX processor 1518 at theData Processing System 1524 and TX/RX processor 1558 at the DataProcessing System 1566) and/or a central processing unit (CPU) (e.g.,CPU 1520 at the Data Processing System 1524 and CPU 1560 at the DataProcessing System 1564) and/or a graphical processing unit (GPU) (e.g.,GPU 1522 at the Data Processing System 1524 and GPU 1562 at the DataProcessing System 1564).

The Memory 1512 may have interfaces with the Data Processing System 1524and the Memory 1552 may have interfaces with Data Processing System1564, respectively. The Memory 1512 or the Memory 1552 may includenon-transitory computer readable mediums (e.g., Storage Medium 1510 atthe Memory 1512 and Storage Medium 1550 at the Memory 1552) that maystore software code or instructions that may be executed by the DataProcessing System 1524 and Data Processing System 1564, respectively, toimplement the processes described in the present disclosure. The Memory1512 or the Memory 1552 may include random-access memory (RAM) (e.g.,RAM 1506 at the Memory 1512 or RAM 1546 at the Memory 1552) or read-onlymemory (ROM) (e.g., ROM 1508 at the Memory 1512 or ROM 1548 at theMemory 1552) to store data and/or software codes.

The Data Processing System 1524 and/or the Data Processing System 1564may be connected to other components such as a GPS module 1514 and a GPSmodule 1554, respectively, wherein the GPS module 1514 and a GPS module1554 may enable delivery of location information of the wireless device1502 to the Data Processing System 1524 and location information of thebase station 1542 to the Data Processing System 1564. One or more otherperipheral components (e.g., Peripheral Component(s) 1504 or PeripheralComponent(s) 1544) may be configured and connected to the dataProcessing System 1524 and data Processing System 1564, respectively.

In example embodiments, a wireless device may be configured withparameters and/or configuration arrangements. For example, theconfiguration of the wireless device with parameters and/orconfiguration arrangements may be based on one or more control messagesthat may be used to configure the wireless device to implement processesand/or actions. The wireless device may be configured with theparameters and/or the configuration arrangements regardless of thewireless device being in operation or not in operation. For example,software, firmware, memory, hardware and/or a combination thereof and/oralike may be configured in a wireless device regardless of the wirelessdevice being in operation or not operation. The configured parametersand/or settings may influence the actions and/or processes performed bythe wireless device when in operation.

In example embodiments, a wireless device may receive one or moremessage comprising configuration parameters. For example, the one ormore messages may comprise radio resource control (RRC) messages. Aparameter of the configuration parameters may be in at least one of theone or more messages. The one or more messages may comprise informationelement (IEs). An information element may be a structural element thatincludes single or multiple fields. The fields in an IE may beindividual contents of the IE. The terms configuration parameter, IE andfield may be used equally in this disclosure. The IEs may be implementedusing a nested structure, wherein an IE may include one or more otherIEs and an IE of the one or more other IEs may include one or moreadditional IEs. With this structure, a parent IE contains all theoffspring IEs as well. For example, a first IE containing a second IE,the second IE containing a third IE, and the third IE containing afourth IE may imply that the first IE contains the third IE and thefourth IE.

In an example, a DCI format 2_1 may be used for notifying the PRB(s) andOFDM symbol(s) where UE may assume no transmission is intended for theUE. The following information may be transmitted by means of the DCIformat 2_1 with CRC scrambled by INT-RNTI: Pre-emption indication 1,Pre-emption indication 2, . . . , Pre-emption indication N. The size ofDCI format 2_1 may be configurable by higher layers up to 126 bits. Apre-emption indication is 14 bits.

In an example, a UE may receive configuration parameters comprising aDownlinkPreemption IE. The UE may be configured with an INT-RNTIprovided by int-RNTI for monitoring PDCCH conveying DCI format 2_1. TheUE may be additionally configured with: a set of serving cells byint-ConfigurationPerServingCell that includes a set of serving cellindexes provided by corresponding servingCellId and a corresponding setof locations for fields in DCI format 2_1 by positionInDCI; aninformation payload size for DCI format 2_1 by dci-PayloadSize; anindication granularity for time-frequency resources by timeFrequencySet.

In an example, if a UE detects a DCI format 2_1 for a serving cell fromthe configured set of serving cells, the UE may assume that notransmission to the UE is present in PRBs and in symbols that areindicated by the DCI format 2_1, from a set of PRBs and a set of symbolsof the last monitoring period. The indication by the DCI format 2_1 maynot be applicable to receptions of SS/PBCH blocks.

In an example, the set of PRBs may be equal to the active DL BWP asdefined in Subclause 12 and may include B_(INT) PRBs. In an example, ifa UE detects a DCI format 2_1 in a PDCCH transmitted in a CORESET in aslot, the set of symbols may be the last N_(symb)^(slot)·T_(INT)·2^(μ-μ) ^(INT) symbols prior to the first symbol of theCORESET in the slot where T_(INT) may be the PDCCH monitoringperiodicity provided by the value of monitoringSlotPeriodicityAndOffsetN_(symb) ^(slot) is the number of symbols per slot, μ may be the SCSconfiguration for a serving cell with mapping to a respective field inthe DCI format 2_1, μ_(INT) may be the SCS configuration of the DL BWPwhere the UE may receive the PDCCH with the DCI format 2_1. In anexample, if the UE is provided tdd-UL-DL-ConfigurationCommon, symbolsindicated as uplink by tdd-UL-DL-ConfigurationCommon may be excludedfrom the last N_(symb) ^(slot)·T_(INT)·2^(μ-μ) ^(INT) symbols prior tothe first symbol of the CORESET in the slot. The resulting set ofsymbols may include a number of symbols that is denoted as N_(INT).

In an example, the UE may be provided the indication granularity for theset of PRBs and for the set of symbols by timeFrequencySet. In anexample, if the value of timeFrequencySet is 0, 14 bits of a field inDCI format 2_1 may have a one-to-one mapping with 14 groups ofconsecutive symbols from the set of symbols where each of the firstN_(INT)−[N_(INT)/14]·14 symbol groups includes [N_(INT)/14] symbols,each of the last 14−N_(INT)+[N_(INT)/14]·14 symbol groups may include[N_(INT)/14] symbols, a bit value of 0 may indicate transmission to theUE in the corresponding symbol group and a bit value of 1 may indicateno transmission to the UE in the corresponding symbol group.

In an example, if the value of timeFrequencySet is 1, 7 pairs of bits ofa field in the DCI format 2_1 may have a one-to-one mapping with 7groups of consecutive symbols where each of the firstN_(INT)−[N_(INT)/7]·7 symbol groups includes [N_(INT)/7] symbols, eachof the last 7−N_(INT)+[N_(INT)/7]·7 symbol groups may include[N_(INT)/7] symbols, a first bit in a pair of bits for a symbol groupmay be applicable to the subset of first [B_(INT)/2] PRBs from the setof B_(INT) PRBs, a second bit in the pair of bits for the symbol groupmay be applicable to the subset of last [B_(INT)/2] PRBs from the set ofB_(INT) PRBs, a bit value of 0 may indicate transmission to the UE inthe corresponding symbol group and subset of PRBs, and a bit value of 1may indicate no transmission to the UE in the corresponding symbol groupand subset of PRBs.

In an example, an IE DownlinkPreemption may be used to configure the UEto monitor PDCCH for the INT-RNTI (interruption). The DownlinkPreemptionmay comprise one or more of following parameters: a dci-PayloadSizeparameter indicating total length of the DCI payload scrambled withINT-RNTI; an int-ConfigurationPerServingCell parameter indicating (perserving cell) the position of the 14 bit INT values inside the DCIpayload; an int-RNTI parameter indicating RNTI used for indicationpre-emption in DL; a timeFrequencySet parameter indicating set selectionfor DL-preemption indication, wherein the set may determine how the UEmay interpret the DL preemption DCI payload; and a positionInDCIparameter indicating starting position (in number of bit) of the 14 bitINT value applicable for this serving cell (servingCellId) within theDCI payload wherein the positionInDCI may be be multiples of 14 (bit).

In an example, a MAC entity of a wireless device may be configured byRRC with a discontinuous reception (DRX) functionality that may controlsthe UE's PDCCH monitoring activity for the MAC entity's one or more RNTI(e.g., C-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, and TPC-SRS-RNTI). The MAC entity may monitor the PDCCHdiscontinuously for the activated Serving Cells using the DRX operationwhen the UE is in RRC_CONNECTED state and if DRX is configured.

In an example, RRC may control DRX operation by configuring one or moreof the following parameters: drx-onDurationTimer: the duration at thebeginning of a DRX Cycle; drx-SlotOffset: the delay before starting thedrx-onDurationTimer; drx-InactivityTimer: the duration after the PDCCHoccasion in which a PDCCH indicates a new UL or DL transmission for theMAC entity; drx-RetransmissionTimerDL (per DL HARQ process except forthe broadcast process): the maximum duration until a DL retransmissionis received; drx-RetransmissionTimerUL (per UL HARQ process): themaximum duration until a grant for UL retransmission is received;drx-LongCycleStartOffset: the Long DRX cycle and drx-StartOffset whichdefines the subframe where the Long and Short DRX Cycle starts;drx-ShortCycle (optional): the Short DRX cycle; drx-ShortCycleTimer(optional): the duration the UE shall follow the Short DRX cycle;drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcastprocess): the minimum duration before a DL assignment for HARQretransmission is expected by the MAC entity; drx-HARQ-RTT-TimerUL (perUL HARQ process): the minimum duration before a UL HARQ retransmissiongrant is expected by the MAC entity.

In an example, when a DRX cycle is configured, the Active Time mayinclude the time while:drx-onDurationTimer or drx-InactivityTimer ordrx-RetransmissionTimerDL or drx-RetransmissionTimerUL orra-ContentionResolutionTimer is running; or a Scheduling Request is senton PUCCH and is pending; or a PDCCH indicating a new transmissionaddressed to the C-RNTI of the MAC entity has not been received aftersuccessful reception of a Random Access Response for the Random AccessPreamble not selected by the MAC entity among the contention-basedRandom Access Preamble.

In an example, when DRX is configured, if a MAC PDU is received in aconfigured downlink assignment, the MAC entity may start thedrx-HARQ-RTT-TimerDL for the corresponding HARQ process in the firstsymbol after the end of the corresponding transmission carrying the DLHARQ feedback; and stop the drx-RetransmissionTimerDL for thecorresponding HARQ process.

In an example, when DRX is configured, if a MAC PDU is transmitted in aconfigured uplink grant, the MAC entity may start thedrx-HARQ-RTT-TimerUL for the corresponding HARQ process in the firstsymbol after the end of the first repetition of the corresponding PUSCHtransmission; and stop the drx-RetransmissionTimerUL for thecorresponding HARQ process.

In an example, when DRX is configured, if a drx-HARQ-RTT-TimerDLexpires: if the data of the corresponding HARQ process was notsuccessfully decoded: the MAC entty may start thedrx-RetransmissionTimerDL for the corresponding HARQ process in thefirst symbol after the expiry of drx-HARQ-RTT-TimerDL.

In an example, when DRX is configured, if a drx-HARQ-RTT-TimerULexpires: the MAC entity may start the drx-RetransmissionTimerUL for thecorresponding HARQ process in the first symbol after the expiry ofdrx-HARQ-RTT-TimerUL.

In an example, when DRX is configured, if a DRX Command MAC CE or a LongDRX Command MAC CE is received: the MAC entity may stopdrx-onDurationTimer; and stop drx-InactivityTimer.

In an example, when DRX is configured, if drx-InactivityTimer expires ora DRX Command MAC CE is received: if the Short DRX cycle is configured:the MAC entity may start or restart drx-ShortCycleTimer in the firstsymbol after the expiry of drx-InactivityTimer or in the first symbolafter the end of DRX Command MAC CE reception; and use the Short DRXCycle.

In an example, when DRX is configured, if drx-InactivityTimer expires ora DRX Command MAC CE is received: if the Short DRX cycle is notconfigured: the MAC entity may use the Long DRX cycle.

In an example, when DRX is configured, if drx-ShortCycleTimer expires:the MAC entity may use the Long DRX cycle.

In an example, when DRX is configured, if a Long DRX Command MAC CE isreceived: the MAC entity may stop drx-ShortCycleTimer; and use the LongDRX cycle.

In an example, if the Short DRX Cycle is used, and [(SFN×10)+subframenumber] modulo (drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle); or if the Long DRX Cycle is used, and[(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset: theMAC entity may start drx-onDurationTimer after drx-SlotOffset from thebeginning of the subframe.

In an example, when DRX is configured, if the MAC entity is in ActiveTime: the MAC entity may monitor the PDCCH. If the PDCCH indicates a DLtransmission: the MAC entity may start the drx-HARQ-RTT-TimerDL for thecorresponding HARQ process in the first symbol after the end of thecorresponding transmission carrying the DL HARQ feedback; and stop thedrx-RetransmissionTimerDL for the corresponding HARQ process. If thePDCCH indicates a UL transmission: the MAC entity may start thedrx-HARQ-RTT-TimerUL for the corresponding HARQ process in the firstsymbol after the end of the first repetition of the corresponding PUSCHtransmission; and stop the drx-RetransmissionTimerUL for thecorresponding HARQ process. If the PDCCH indicates a new transmission(DL or UL): the MAC entity may start or restart drx-InactivityTimer inthe first symbol after the end of the PDCCH reception.

In an example, when DRX is configured, in current symbol n, if the MACentity would not be in Active Time considering grants/assignments/DRXCommand MAC CE/Long DRX Command MAC CE received and Scheduling Requestsent until 4 ms prior to symbol n when evaluating DRX Active Timeconditions: the MAC entity may not transmit periodic SRS andsemi-persistent SRS; and the MAC entity may not report CSI on PUCCH andsemi-persistent CSI on PUSCH.

In an example, when DRX is configured, if CSI masking (csi-Mask) issetup by upper layers: in current symbol n, if drx-onDurationTimer wouldnot be running considering grants/assignments/DRX Command MAC CE/LongDRX Command MAC CE received until 4 ms prior to symbol n when evaluatingDRX Active Time conditions: the MAC entity may not report CSI on PUCCH.

In an example, regardless of whether the MAC entity is monitoring PDCCHor not, the MAC entity may transmit HARQ feedback, aperiodic CSI onPUSCH, and aperiodic SRS when such is expected.

In an example, the MAC entity may need not to monitor the PDCCH if it isnot a complete PDCCH occasion (e.g. the Active Time starts or ends inthe middle of a PDCCH occasion).

In an example, PDCCH may be used for UL cancelation indication. In anexample, based on detecting an UL cancelation indication, the wirelessdevice may stop an uplink transmission without resuming. In an example,the UL transmission may include one or more of dynamically scheduled ULtransmissions (e.g., PUSCH, PUCCH, and SRS), semi-persistent ULtransmissions (e.g., PUSCH, PUCCH, SRS), Periodic UL transmissions(e.g., configured grant PUSCH, PUCCH, SRS) and PRACH.

In an example, the UL cancellation indication may be indicated using agroup common DCI.

In an example, a time/frequency region may be provided in thecancelation indication DCI for a group of UEs to derive the ULcancelation behavior. In an example, UL cancellation indication may beseparately provided for each UE in a group common DCI.

In an example, for a UE supporting UL cancellation, the UE may beconfigured with slot-level or mini-slot level monitoring for ULcancellation indication monitoring. For mini-slot level monitoring,monitoring occasion and number for blind decoding for UL cancellationindication may be configurable.

In an example, upon receiving UL cancellation indication, UE maydetermine the starting position of cancelled time resources based on oneor more of the following: slot and/or symbol offset indicated by DCIrelative to the ending symbol PDCCH CORESET carrying the UL cancellationindication plus the minimum UE processing time for cancelationoperation; slot and/or symbol offset configured by RRC relative to theending symbol PDCCH CORESET carrying the UL cancellation indication plusthe minimum UE processing time for cancelation operation; andsymbol-level offset implicitly determined based on the ending symbolPDCCH CORESET carrying the UL cancellation indication plus the minimumUE processing time for cancelation operation.

In an example, a wireless device may apply the UL cancellation in oneslot. The UE may cancel the UL transmission in one slot given by ULcancellation indication until the boundary of the slot. In an example,UL cancellation may be applied for multiple slots.

In an example, for UL transmission with associated PDCCH, UE may startUL CI monitoring after the PDCCH is decoded. In an example, UE maymonitor UL CI at least at the latest monitoring occasion ending no laterthan X symbols before the start of the UL transmission, and X may berelated to UL CI processing time. For UL transmission without associatedPDCCH, UE may monitor UL CI at least at the latest monitoring occasionthat ends no later than X symbols before the start of the ULtransmission, In an example, the RRC configuration parameters for ULcancellation indication may indicate a new RNTI (e.g. CI-RNTI) for ULCancellation Indication. The DCI payload size for UL CI may beconfigured by RRC.

In an example, for UL transmissions with and without associated PDCCH,UE may start monitoring UL CI at least at the latest monitoring occasionending no later than X symbols before the start of the UL transmission,and X may be related to UL CI processing time. The UE may stopmonitoring UL CI from X symbols before the end of relevant ULtransmission, and X may be related to UL CI processing time.

In an example, a MAC entity of the wireless device may not generate aMAC PDU for the HARQ entity based on the one or more of followingconditions being satisfied: the MAC entity being configured with a firstskipping parameter (e.g., skipUplinkTxDynamic) with value true and thegrant indicated to the HARQ entity being addressed to one or more RNTIs(e.g., a C-RNTI), or the grant indicated to the HARQ entity being aconfigured uplink grant; no aperiodic CSI being requested for a PUSCHtransmission; the MAC PDU including zero MAC SDUs; the MAC PDU includingonly the periodic BSR and no data being available for any LCG, or theMAC PDU including only the padding BSR. In an example, the skippingparameter may be configured for a cell group (e.g., a MAC cell groupand/or MAC entity). The skipping parameter may be a Boolean parametertaking a value of true or false. The wireless device may receive an RRCmessage indicating the skipping parameter. The skipping process may bebased on a wireless device capability and the base station may configurethe skipping for a wireless device based on the wireless devicesupporting this capability. In an example, the wireless device maytransmit, to the base station, one or more messages comprising aplurality of wireless device capabilities including the wireless devicecapability to support skipping.

In an example, a MAC entity of a wireless device may be configured witha plurality of secondary cells (SCells). Based on the MAC entity beingconfigured with one or more SCells, the network may activate and/ordeactivate the configured SCells. Upon configuration of an SCell, theSCell may be deactivated.

The configured SCell(s) may be activated and/or deactivated by:receiving an SCell Activation/Deactivation MAC CE; configuringsCellDeactivationTimer timer per configured SCell (except the SCellconfigured with PUCCH, if any) and an SCell being deactivated based onthe associated SCell deactivation timer expiring.

In an example, if an SCell Activation/Deactivation MAC CE is receivedindicating activation of an SCell, the MAC entity may activate the SCellaccording to a timing. The activating the SCell may comprise applyingnormal SCell operations including SRS transmissions on the SCell; CSIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; PUCCH transmissions on the SCell, if configured. If theSCell was deactivated prior to receiving this SCellActivation/Deactivation MAC CE: the MAC entity may activate the DL BWPand UL BWP indicated by firstActiveDownlinkBWP-Id andfirstActiveUplinkBWP-Id respectively. The MAC entity may start orrestart the sCellDeactivationTimer associated with the SCell accordingto a timing. The MAC entity may (re-)initialize suspended configureduplink grants of configured grant Type 1 associated with the SCellaccording to the stored configuration, if any, and to start in thesymbol according to rules. The MAC entity may trigger power headroomreport (PHR).

In an example, if an SCell Activation/Deactivation MAC CE is receivedindicating deactivation of the SCell; or if the sCellDeactivationTimerassociated with the activated SCell expires: the MAC entity maydeactivate the SCell according to a timing; the MAC entity may stop thesCellDeactivationTimer associated with the SCell; the MAC entity maystop the bwp-InactivityTimer associated with the SCell; the MAC entitymay deactivate any active BWP associated with the SCell; the MAC entitymay clear any configured downlink assignment and any configured uplinkgrant Type 2 associated with the SCell respectively; the MAC entity mayclear any PUSCH resource for semi-persistent CSI reporting associatedwith the SCell; the MAC entity may suspend any configured uplink grantType 1 associated with the SCell; the MAC entity may flush HARQ buffersassociated with the SCell.

In an example, if PDCCH on the activated SCell indicates an uplink grantor downlink assignment; or if PDCCH on the Serving Cell scheduling theactivated SCell indicates an uplink grant or a downlink assignment forthe activated SCell; or if a MAC PDU is transmitted in a configureduplink grant or received in a configured downlink assignment: the MACentity may restart the sCellDeactivationTimer associated with the SCell.

In an example, if the SCell is deactivated: the MAC entity may nottransmit SRS on the SCell; the MAC entity may not report CSI for theSCell; the MAC entity may not transmit on UL-SCH on the SCell; the MACentity may not transmit on RACH on the SCell; the MAC entity may notmonitor the PDCCH on the SCell; the MAC entiy may not monitor the PDCCHfor the SCell; and the MAC entity may not transmit PUCCH on the SCell.

In an example, HARQ feedback for a MAC PDU containing SCellActivation/Deactivation MAC CE may not be impacted by PCell, PSCell andPUCCH SCell interruptions due to SCell activation/deactivation. In anexample, when SCell is deactivated, the ongoing Random Access procedureon the SCell, if any, may be aborted.

Example embodiments may operate considering different traffic/servicetypes including enhanced mobile broadband (eMBB) traffic/service typeand ultra-reliable low-latency communications (URLLC) traffic/servicetypes. The eMBB traffic/service type may be related to high data rateapplications where latency and reliability requirements may not be asstrict as the data rate requirements. The URLLC applications may havestrict requirements on latency and reliability and may requirecomparatively lower data rates than the eMBB traffic/service type.

In example embodiments and as shown in FIG. 16, a wireless device may bescheduled with an uplink transmission and may stop the uplinktransmission due to receiving an uplink cancellation indicationindicating radio resources that overlap with the uplink transmission. Inan example, in response to the radio resources indicated by the uplinkcancellation indication staring before the scheduled the resources, thewireless device may not start the uplink scheduled transmission. In anexample the scheduled uplink transmission may correspond to an eMBBtraffic/service type and the base station may indicate the uplinkcancellation so that the resources indicated by the uplink cancellationmay be used for scheduling transmissions (e.g., transport blocks)corresponding to URLLC traffic/service type. As shown in FIG. 16, thewireless device may start its scheduled uplink transmission due touplink cancellation indication indicating resources that has overlapwith the scheduled resources. The wireless device may not resume itstransmission of the scheduled uplink transmission even if the cancelledresources end before the scheduled uplink transmission ends. Thewireless device may receive a DCI, associated with an RNTI indicatinguplink cancellation indication, comprising a plurality of uplinkcancellation indications including an uplink cancellation indicationrelated to the scheduled uplink transmission. The DCI may determine arelevant uplink cancellation indication based on one or moreconfiguration parameters (e.g., uplink cancellation indicationconfiguration parameters).

In an example, for a DL BWP configured to a UE in a serving cell, the UEmay be provided by higher layers with a number of search space setswherein, for a search space set from the search space sets, the UE maybe provided one or more of the following by the IE SearchSpace: a searchspace set index s, by searchSpaceId, an association between the searchspace set s and a CORESET p by controlResourceSetId, a PDCCH monitoringperiodicity of ks slots and a PDCCH monitoring offset, bymonitoringSlotPeriodicityAndOffset, a PDCCH monitoring pattern within aslot, indicating first symbol(s) of the CORESET within a slot for PDCCHmonitoring, by monitoringSymbolsWithinSlot, a duration of slotsindicating a number of slots that the search space set s may exist byduration, a number of PDCCH candidates M_(s) ^((L)) per CCE aggregationlevel L by aggregationLevel1, aggregationLevel2, aggregationLevel4,aggregationLevel8, and aggregationLevel16, for CCE aggregation level 1,CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level8, and CCE aggregation level 16, respectively, an indication that searchspace set s is either a CSS set or a USS set by searchSpaceType, ifsearch space set s is a CSS set, an indication bydci-Format0-0-AndFormat1-0 to monitor PDCCH candidates for DCI format0_0 and DCI format 1_0, an indication by dci-Format2-0 to monitor one ortwo PDCCH candidates for DCI format 2_0 and a corresponding CCEaggregation level, an indication by dci-Format2-1 to monitor PDCCHcandidates for DCI format 2_1, an indication by dci-Format2-2 to monitorPDCCH candidates for DCI format 2_2, an indication by dci-Format2-3 tomonitor PDCCH candidates for DCI format 2_3, if search space set s is aUSS set, an indication by dci-Formats to monitor PDCCH candidates eitherfor DCI format 0_0 and DCI format 1_0, or for DCI format 0_1 and DCIformat 1_1.

In an example, if the monitoringSymbolsWithinSlot indicates to a UE tomonitor PDCCH in a subset of up to three consecutive symbols that aresame in every slot where the UE monitors PDCCH for all search spacesets, the UE may not expect to be configured with a PDCCH SCS other than15 kHz if the subset includes at least one symbol after the thirdsymbol.

In an example, a UE may not expect to be provided a first symbol and anumber of consecutive symbols for a CORESET that results to a PDCCHcandidate mapping to symbols of different slots.

In an example, a UE may not expect any two PDCCH monitoring occasions onan active DL BWP, for a same search space set or for different searchspace sets, in a same CORESET to be separated by a non-zero number ofsymbols that is smaller than the CORESET duration.

In an example, a UE may determine a PDCCH monitoring occasion on anactive DL BWP from the PDCCH monitoring periodicity, the PDCCHmonitoring offset, and the PDCCH monitoring pattern within a slot. Forsearch space set s, the UE may determine that a PDCCH monitoringoccasion(s) exists in a slot with number n_(s,f) ^(μ) in a frame withnumber n_(f) if (n_(f)·N_(slot) ^(frame,μ)+n_(s,f) ^(μ)−o_(s))modk_(s)=0. The UE may monitor PDCCH candidates for search space set s forT_(s) consecutive slots, starting from slot n_(s,f) ^(μ), and may notmonitor PDCCH candidates for search space set s for the next k_(s)-T_(s)consecutive slots.

Uplink cancellation mechanism may be used by a base station to cancelscheduled uplink transmissions for one or more wireless devices. Theresources of the scheduled uplink transmissions may be used for otheruplink transmissions that have strict delay and reliability requirements(for example, in URLLC applications). The uplink cancellation mechanismsmay be indicated using downlink control channel signaling. It isimportant that the wireless devices monitors the downlink controlchannel to receive the signaling for the uplink cancellationindications. Existing control channel monitoring technologies may leadto a wireless device not monitoring the downlink control channel and notreceiving an uplink cancellation indication. This may cause collisionwith the URLLC uplink transmissions leading to performance degradationof URLLC applications (for example increased delay and reducedreliability). There is a need to enhance the existing control channelmonitoring technologies to enhance the URLLC performance and enable theURLLC strict delay and reliability requirements. Example embodimentsenhance the control channel monitoring technologies.

In an example embodiment as shown in FIG. 17, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. The one ormore messages may comprise uplink cancellation indication configurationparameters. The uplink cancellation indication configuration parametersmay comprise a first radio network temporary identifier (RNTI)associated with uplink cancellation indication. The first RNTI may becalled a cancellation indication RNTI (e.g., CI-RNTI). The uplinkcancellation indication configuration parameters may comprise otherparameters comprising first parameters for determining an uplinkcancellation indication for the wireless device in a DCI that includes aplurality of uplink cancellation indications. The one or more messagesmay further comprise discontinuous reception (DRX) configurationparameters. The DRX configuration parameters may comprise values of oneor more timers and/or other parameters used by a DRX procedure at thewireless device for determining whether the wireless device is in DRXActive Time or not. The DRX configuration parameters may control thewireless device control channel monitoring behavior.

The wireless device may monitor a common search space of a downlinkcontrol channel for the first RNTI (e.g., RNTI associated with uplinkcancellation indication), and when such monitoring for the first RNTI isexpected, regardless of the wireless device being in a DRX Active timeor not. In an example, the wireless device may monitor a common searchspace of a downlink control channel for the first RNTI, and when suchmonitoring for the first RNTI is expected, regardless of the wirelessdevice being in a DRX Active time or not and in one or more downlinkcontrol channel (e.g.,. PDCCH) monitoring occasions. A PDCCH monitoringoccasion may be a time duration (e.g., one or a consecutive number ofsymbols) during which the MAC entity may be configured to monitor thePDCCH.

The monitoring for the first RNTI may be expected in a time window thatmay be defined based on the timing of a reception of signalingindicating/scheduling the scheduled uplink transmission (e.g., ascheduling DCI) and/or a timing of the scheduled uplink transmission. Inan example, the time window may be further based on a processing timefor the scheduled uplink transmission and/or a capability of thewireless device (e.g., processing time capability). The wireless devicemay transmit, to the base station, a parameter indicating the capability(e.g., in a capability message indicating one or more wireless devicecapabilities). In an example, the time window may end at an offsetbefore the timing of the scheduled uplink transmission, wherein theoffset may be based on the processing time. In an example, the timewindow may have a fixed duration. The wireless device may determine thestarting time of the time window based on the ending time of the timewindow and the duration of the time window. In an example, the timewindow may start based on a timing of reception of the signalingindicating the scheduled uplink transmission. In an example, the timewindow may start at or an offset after the timing of reception of thesignaling indicating the scheduled uplink transmission.

In an example, when the monitoring for the first RNTI is not expected(e.g., outside the time window), the wireless device may monitor thedownlink control channel for the first RNTI based on the DRX procedure.For example, when the monitoring for the first RNTI is not expected, thewireless device may monitor the downlink control channel for the firstRNTI based on the wireless device being in the DRX Active Time and/orthe wireless device may not monitor the downlink control channel for thefirst RNTI based on the wireless device not being in DRX Active Time.

In an example, when monitoring for the first RNTI is not expected, thewireless device may not monitor the downlink control channel for thefirst RNTI regardless of the wireless device being in a DRX Active Timeor not. The wireless device may monitor the first RNTI regardless of theDRX procedures and/or the monitoring behavior of the wireless device forfirst RNTI may not be controlled by the DRX procedures.

Based on the monitoring the common search space of the control channel,the wireless device may receive a DCI associated with the first RNTI,wherein the DCI comprises and/or indicates an uplink cancellationindication indicating cancellation of uplink transmission on first radioresources of a scheduled uplink transmission. In an example, thescheduled uplink transmission may be for transmission of one or moretransport blocks and/or uplink control information (UCI) via an uplinkshared channel. In an example, the scheduled uplink transmission may bebased on a configured grant. In an example, the scheduled uplinktransmission may be dynamically scheduled and/or may be based on ascheduling DCI indicating an uplink grant for the scheduled uplinktransmission. In an example, the scheduled uplink transmission may befor transmission of a signal. In an example, the signal may be soundingreference signal (SRS). The uplink cancellation indication may indicateone or more symbols and a plurality resource blocks wherein the wirelessdevice may cancel its scheduled uplink transmission and/or the wirelessdevice may stop its uplink transmission on the radio resources indicatedby the uplink cancellation indication (e.g., at the starting symbolindicated by the uplink cancellation indication). In an example, thecancellation of the uplink transmission may start at a time that iswithin the scheduled uplink transmission (e.g., after the scheduleduplink transmission has started).

In an example, the scheduled uplink transmission may be via second radioresources and the first radio resources of the uplink transmission (tobe cancelled based on the uplink cancellation indication) may be asubset of the second resources. In an example, the cancellation of theuplink transmission may be before or when the scheduled uplinktransmission begins. In an example, the wireless device may not resumetransmission of the scheduled uplink transmission after the uplinkcancellation ends even if the scheduled uplink transmission ends afterthe uplink cancellation ends. The wireless device may determine the oneor more symbols and the plurality of resource blocks for uplinkcancellation based on the uplink cancellation indication indicated bythe DCI and one or more configuration parameters configured by RRC. Thewireless device may cancel the uplink transmission based on receivingthe downlink control information.

In an example embodiment as shown in FIG. 18 and FIG. 19, the wirelessdevice may receive a first downlink control information indicating afirst uplink transmission. In an example, the first downlink controlinformation may comprise an uplink grant indicating the first uplinktransmission. In an example, the first downlink control information mayindicate a second uplink transmission comprising the first uplinktransmission, wherein first radio resources for transmission of thefirst uplink transmission may be a subset of second radio resources fortransmission of the second uplink transmission. A resource allocationfield of the first downlink control information may indicate the secondradio resources of the second uplink transmission. The first downlinkcontrol information indicating the second uplink transmission mayindicate transmission via an uplink channel such as transmission of oneor more transport blocks and/or UCI or may indicate transmission of anuplink signal (e.g., SRS).

The wireless device may determine, based on the DRX procedures, ActiveTime for control channel monitoring. The determination of the ActiveTime may be based on one or more DRX timers configured for the wirelessdevice running or based on other criteria. The wireless device maymonitor a common search space of a downlink control channel for thefirst RNTI (e.g., RNTI associated with uplink cancellation indication),and when such monitoring for the first RNTI is expected, regardless ofthe wireless device being in a DRX Active time or not. In an example,the wireless device may monitor a common search space of a downlinkcontrol channel for the first RNTI, and when such monitoring for thefirst RNTI is expected, regardless of the wireless device being in a DRXActive time or not and in one or more downlink control channel (e.g.,.PDCCH) monitoring occasions.

In an example, the first downlink control information may be received ata first timing. The first uplink transmission (e.g., the uplinktransmission to be cancelled by the cancellation indication) may startat the second timing and the second downlink control information,associated with the first RNTI, may be expected between the first timingand the second timing.

In an example, the first downlink control information may be received ata first timing. The second uplink transmission (e.g., the uplinktransmission scheduled by the first DCI) may start at the second timingand the second downlink control information, associated with the firstRNTI, may be expected between the first timing and the second timing.

In an example, the second downlink control information, associated withthe first RNTI, may be expected between a first offset after the firsttiming and the second timing. In an example, the second downlink controlinformation, associated with the first RNTI, may be expected between thefirst timing and a second offset before the second timing. In anexample, the second downlink control information, associated with thefirst RNTI, may be expected between a first offset after the firsttiming and a second offset before the second timing. In an example, thefirst offset and/or the second offset may be configured by RRC. In anexample, the first offset and/or the second offset may bepre-defined/pre-configured. In an example, the second offset may bebased on a processing time. In an example, the second offset may bebased on a capability of the wireless device. The wireless device maytransmit, to the base station, one or more messages (e.g., one or morecapability messages) and may indicate the capability indicating thesecond offset.

Based on the monitoring the common search space of the control channel,the wireless device may receive a second DCI associated with the firstRNTI, wherein the second DCI may comprise and/or may indicate an uplinkcancellation indication indicating cancellation of the first uplinktransmission. The uplink cancellation indication may indicate one ormore symbols and a plurality resource blocks wherein the wireless devicemay cancel first uplink transmission of the second uplink transmissionand/or the wireless device may stop the second uplink transmission onthe radio resources indicated by the uplink cancellation indication thathave overlap with radio resources of the second uplink transmission(e.g., at the starting symbol indicated by the uplink cancellationindication). In an example, the cancellation of the first uplinktransmission may be within the second uplink transmission (e.g., afterthe second uplink transmission has started).

In an example, the second downlink control information may comprise aplurality of uplink cancellation indications comprising a first uplinkcancellation indication indicating cancellation of the first uplinktransmission. The second DCI may comprise a plurality of uplinkcancellation indications for one or more wireless devices. The firstuplink cancellation indication may indicate cancelation of a pluralityof resources comprising resources for transmission of the first uplinktransmission. The wireless device may determine the first cancellationindication in the plurality of cancellation indications of the seconddownlink control information. In an example, the uplink cancellationindication configuration parameters may comprise one or more parameters,wherein the determining the first uplink cancellation indication may bebased on the one or more parameters.

In an example embodiment as shown in FIG. 20, a wireless device mayreceive one or more messages comprising uplink cancellation indicationconfiguration parameters, discontinuous reception (DRX) configurationparameters and periodic resources configuration parameters. In anexample, the periodic resources configuration parameters may be for oneor more configured grant configurations. In an example, the periodicresources configuration parameters may be sounding reference signal(SRS) configurations (e.g., periodic SRS resources and/or periodic SRStransmission configuration parameters).

The wireless device may determine, based on the DRX procedures, ActiveTime for control channel monitoring. The determination of the ActiveTime may be based on one or more DRX timers configured for the wirelessdevice running or based on other criteria. The wireless device maymonitor a common search space of a downlink control channel for thefirst RNTI (e.g., RNTI associated with uplink cancellation indication),and when such monitoring for the first RNTI is expected, regardless ofthe wireless device being in a DRX Active time or not. The wirelessdevice may monitor a common search space of a downlink control channelfor the first RNTI (e.g., RNTI associated with uplink cancellationindication), and when such monitoring for the first RNTI is expected andin one or more control channel (e.g., PDCCH) monitoring occasions,regardless of the wireless device being in a DRX Active time or not.

Based on the monitoring the common search space of the control channel,the wireless device may receive a second DCI associated with the firstRNTI, wherein the second DCI may comprise and/or may indicate an uplinkcancellation indication indicating cancellation of a first uplinktransmission and wherein the first uplink transmission may be based onthe periodic resources configuration parameters. The uplink cancellationindication may indicate one or more symbols and a plurality resourceblocks wherein the wireless device may cancel the first uplinktransmission. The wireless device may cancel the first uplinktransmission based on the receiving the second downlink control channel.

In an example, the first uplink transmission may be scheduled at a firsttiming. The second DCI, associated with the first RNTI, may be expectedbefore the first timing. In an example, the second DCI may be expectedon or before an offset before the first timing. In an example, theoffset may be configurable by RRC and/or an RRC configuration parametermay indicate the offset. In an example, the offset may bepre-configured/pre-defined. In an example, the offset may be based on aprocessing time and/or a capability of the wireless device. The wirelessdevice may include the capability/processing time in a capabilitymessage comprising a plurality of wireless device capabilities andtransmit the capability message to the base station.

In an example, the wireless device may receive a command/controlinformation indicating activation of periodic resources based on theperiodic resources configuration parameters. The command/controlinformation may be based on MAC control signaling (e.g., a MAC commandsuch as MAC CE) or physical layer control signaling (e.g., a DCI).

In an example, the command/control information for activation of theperiodic resources may be a downlink control information received via adownlink control channel. The periodic resources may be configured grantresources and the periodic resources configuration may be configuredgrant configuration. In an example, a second uplink transmission maycomprise the first uplink transmission. The first radio resources of thefirst uplink transmission may be a subset of second radio resources ofthe second uplink transmission. The second uplink transmission may bebased on the configured grant/periodic resources configurationparameters.

In an example, the command/control information may be a MAC CEindicating activation of periodic SRS resources. The periodic resourcesmay be periodic SRS resources and the periodic resources configurationmay be periodic SRS configuration. A second uplink transmission,comprising the first uplink transmission, may be an SRS transmissionbased on the periodic SRS resources.

In an example, the second downlink control information may comprise aplurality of uplink cancellation indications comprising a first uplinkcancellation indication indicating cancellation of the first uplinktransmission. The second DCI may comprise a plurality of uplinkcancellation indications for one or more wireless devices. The firstuplink cancellation indication may indicate cancelation of a pluralityof resources comprising resources for transmission of the first uplinktransmission. The wireless device may determine the first cancellationindication in the plurality of cancellation indications of the seconddownlink control information. In an example, the uplink cancellationindication configuration parameters may comprise one or more parameters,wherein the determining the first uplink cancellation indication may bebased on the one or more parameters.

In an example embodiment as shown in FIGS. 21 and 22, a wireless devicemay receive one or more messages comprising configuration parameters.The one or more messages may comprise one or more RRC messages. The oneor more messages may comprise uplink cancellation configurationparameters, comprising an RNTI, and configuration parameters of asecondary cell. The uplink cancellation indication configurationparameters may indicate uplink radio resources on which uplinktransmission may be cancelled based on receiving an uplink cancellationindication in a DCI. The uplink cancellation indication configurationparameters may comprise parameters that may be used by the wirelessdevice to determine the radio resources for uplink cancellation.

The wireless device may receive a DCI, associated with the RNTI,indicating cancellation of a scheduled uplink transmission on thesecondary cell. The wireless device may start the deactivation timer ofthe secondary cell based on the receiving the DCI. Based on thedeactivation timer of the secondary cell expiring, the wireless devicemay deactivate the secondary cell.

In an example, the uplink transmission may be a dynamically scheduleduplink transmission or a portion of the dynamically scheduled uplinktransmission (e.g., radio resources of the uplink transmission may be asubset of radio resources of the dynamically scheduled uplinktransmission). The wireless device may receive a second DCI comprisingan uplink grant indicating the uplink transmission. The second DCI maycomprise a resource allocation field indicating radio resources of theuplink transmission (e.g., indicating first resources comprising theradio resources of the uplink transmission).

In an example, the one or more messages may comprise configurationparameters of a configured grant configuration. The uplink transmissionmay be based on the configured grant configuration parameters. Forexample, the configured grant configuration parameters may indicate afirst resource comprising the radio resources of the uplinktransmission. In an example, the wireless device may further receive anactivation DCI indicating activation of the first configured grantconfiguration. The wireless device may activate a plurality of resourcesbased on the receiving the activation DCI, wherein the plurality ofresources may comprise the first resource, wherein the first resourcecomprises radio resources of the uplink transmission. The radioresources of the uplink transmission may be a subset of the firstresource. In an example, the configured grant configuration parametersmay comprise a periodicity parameter, wherein the plurality of resourcesmay be based on the periodicity parameter.

In an example, the wireless device may or may not receive a packet fromupper layers (e.g., MAC layer) for the scheduling transmission. Forexample, an upper layer (e.g., MAC) may determine, based on a skippingprocedure, whether to skip or not skip a scheduled transmission. In anexample, the starting the deactivation timer based on the receiving theDCI (e.g. the uplink cancellation DCI) may be independent of thewireless device having a packet for transmission based on the scheduledtransmission or skipping the scheduled transmission. In an example, thestarting the deactivation timer based on the receiving the DCI (e.g. theuplink cancellation DCI) may be independent of skipping or not skippingthe scheduled transmission.

In an example, the one or more messages may further comprise a parameterindicating a deactivation timer of the secondary cell. The deactivationof the secondary cell may be specific to the secondary cell anddifferent secondary cells may be configured with different deactivationtimer values. The starting the deactivation timer of the secondary cellmay be with configured deactivation timer value.

In an example embodiment, a wireless device may receive one or moremessages comprising: uplink cancellation indication configurationparameters comprising a first radio network temporary identifier (RNTI);and discontinuous reception (DRX) configuration parameters. The wirelessdevice may monitor, for the first radio network identifier and when suchis expected, a common search space regardless of the wireless devicebeing in DRX Active Time or not. Based on the monitoring, the wirelessdevice may receive a downlink control information, associated with thefirst RNTI, indicating cancellation of uplink transmission on firstradio resources of a scheduled uplink transmission. The wireless devicemay cancel the uplink transmission based on the receiving the downlinkcontrol information.

In an example, the scheduled uplink transmission may be via second radioresources; and the first radio resources may be a subset of the secondradio resources.

In an example, the cancelling the uplink transmission may comprisestopping transmission in the middle of the scheduled uplinktransmission.

In an example, scheduled uplink transmission may be for transmission ofa transport block and/or uplink control information via an uplink sharedchannel. In an example, the scheduled uplink transmission is based on aconfigured grant resource. In an example, the scheduled uplinktransmission is dynamically scheduled based on a scheduling DCI.

In an example, the scheduled uplink transmission may be for transmissionof an uplink signal. In an example, the uplink signal may be a soundingreference signal.

In an example embodiment, a wireless device may receive one or moremessages comprising: uplink cancellation indication configurationparameters comprising a first radio network temporary identifier; anddiscontinuous reception (DRX) configuration parameters. The wirelessdevice may receive a first downlink control information indicating afirst uplink transmission. The wireless device may monitor, for thefirst radio network identifier and when such is expected, a commonsearch space regardless of the wireless device being in DRX Active Timeor not. The wireless device may receive, based on the monitoring, asecond downlink control information, associated with the first RNTI,indicating cancellation of the first uplink transmission. The wirelessdevice may cancel the first uplink transmission based on the receivingthe second downlink control information.

In an example, the first downlink transmission may comprise an uplinkgrant indicating the first uplink transmission. In an example, the firstdownlink information may indicate a second uplink transmissioncomprising the first uplink transmission. In an example, first radioresources for transmission of the first uplink transmission may be asubset of second radio resources for transmission of the second uplinktransmission.

In an example, the first downlink control information may be received ata first timing. The first uplink transmission may be scheduled, by thefirst downlink control information, at a second timing. In an example,the second downlink control information, associated with the first radionetwork identifier, may be expected between the first timing and thesecond timing. In an example, the second downlink control information,associated with the first radio network identifier, may be expectedbetween a first offset after the first timing and a second offset beforethe second timing. In an example, the second downlink controlinformation, associated with the first radio network identifier, may beexpected between the first timing and a second offset before the secondtiming. In an example, the second downlink control information,associated with the first radio network identifier, may be expectedbetween a first offset after the first timing and the second timing. Inan example the first offset and/or the second offset may be configured(e.g., by one or more RRC parameters) or may be based on/indicated byone or more RRC parameters. In an example the first offset and/or thesecond offset may have a pre-configured/pre-defined value.

In an example, the first uplink transmission may be via a physicaluplink shared channel.

In an example, the first uplink transmission may be a sounding referencesignal transmission. In an example, a sounding reference signal requestfield of the first downlink control information may indicate thetransmission of the sounding reference signal.

In an example, the wireless device may determine, based on the DRXconfiguration parameters, whether the wireless device is in DRX ActiveTime or not (e.g., when such is expected).

In an example, the second downlink control information may comprise aplurality of uplink cancellation indications comprising a first uplinkcancellation indication indicating cancellation of the first uplinktransmission. In an example, the first uplink cancellation indicationmay indicate a plurality of radio resources comprising radio resourcesfor transmission of the first uplink transmission. In an example, thewireless device may determine the first uplink cancellation indicationin the plurality of uplink cancellation indications. In an example, theuplink cancellation indication configuration parameters may comprise oneor more parameters; and the determining the first uplink cancellationindication, in the plurality of uplink cancellation indications, may bebased on the one or more parameters.

In an example embodiment, a wireless device may receive one or moremessages comprising: uplink cancellation indication configurationparameters comprising a first radio network temporary identifier;discontinuous reception (DRX) configuration parameters; and periodicresources configuration parameters. The wireless device may monitor, forthe first radio network identifier and when such is expected, a commonsearch space regardless of the wireless device being in DRX Active Timeor not. The wireless device may receive, based on the monitoring, asecond downlink control information, associated with the first RNTI,indicating cancellation of a first uplink transmission, wherein thefirst uplink transmission may be based on the periodic resourcesconfiguration parameters. The wireless device may cancel the firstuplink transmission based on the receiving the second downlink controlinformation.

In an example, the wireless device may receive a command/controlinformation indicating activation of periodic resources based on theperiodic resources configuration parameters. In an example, thecommand/control information may be a MAC command. In an example, thecommand/control information may be based on physical layer signaling.

In an example, the control information may be received based on adownlink control channel; and the periodic resources may be configuredgrants. In an example, a second uplink transmission, comprising thefirst uplink transmission, may be based on the configured grantconfiguration parameters. In an example, the first radio resources, fortransmission of the first uplink transmission, may be a subset of secondradio resources for transmission of the second uplink transmission.

In an example, the command may be a MAC control element; and theperiodic resources may be sounding reference signal resources. In anexample, a second uplink transmission, comprising the first uplinktransmission, is a sounding reference signal transmission based on thesounding reference signal resources.

In an example, the first uplink transmission may be scheduled at a firsttiming. The second downlink control information, associated with thefirst radio network identifier, may be expected before the first timing.In an example, the second downlink control information, associated withthe first radio network identifier, may be expected before an offsetbefore the first timing. In an example, the offset may be configuredand/or indicated by an RRC parameter. In an example, the offset may havea pre-configured/pre-defined value. In an example, the offset may bebased on a capability of the wireless device.

In an example, the wireless device may determine, based on the DRXconfiguration parameters, whether the wireless device is in DRX ActiveTime or not (e.g., when such is expected).

In an example, the second downlink control information may comprise aplurality of uplink cancellation indications comprising a first uplinkcancellation indication indicating cancellation of the first uplinktransmission. In an example, the first uplink cancellation may indicatea plurality of radio resources comprising radio resources fortransmission of the first uplink transmission. In an example, thewireless device may determine the first uplink cancellation indicationin the plurality of uplink cancellation indications. In an example, theuplink cancellation indication configuration parameters may comprise oneor more parameters; and the determining the first uplink cancellationindication may be based on the one or more parameters.

In an example embodiment, a wireless device may receive one or moremessages comprising: uplink cancellation configuration parameterscomprising an RNTI; and configuration parameters of a secondary cell.The wireless device may receive a DCI, associated with the RNTI,indicating cancellation of a scheduled uplink transmission on thesecondary cell. The wireless device may start a deactivation timer basedon the receiving the DCI. The wireless device may deactivate thesecondary cell based on the deactivation timer expiring.

In an example, the uplink transmission may be based on a dynamic grantindicated by a second DCI.

In an example, the one or more messages may further comprise configuredgrant configuration parameters of a configured grant configuration; andthe uplink transmission is based on the configured grant configurationparameters. In an example, the wireless device may receive an activationDCI indicating activation of a plurality of resources comprising a firstresource for a first uplink transmission comprising the uplinktransmission. In an example, radio resources of the uplink transmissionmay be a subset of radio resources of the first uplink transmission. Inan example, the configured grant configuration parameters comprise aperiodicity parameter; and the plurality of resources may be based onthe periodicity.

In an example, the starting the deactivation timer based on thereceiving the DCI may be independent of the wireless device having apacket for transmission based on the scheduled transmission or skippingthe scheduled transmission. In an example, the starting the deactivationtimer based on the receiving the DCI may be independent of skipping ornot skipping the scheduled transmission.

In an example, the one or more messages further comprise parameterindicating a deactivation timer value for the secondary cell. In anexample, the starting the deactivation timer may be with thedeactivation timer value.

In an example, the DCI may comprise a plurality of uplink cancellationindications comprising a first uplink cancellation indication indicatingthe cancellation of the uplink transmission of the secondary cell. Thewireless device may determine the first uplink cancellation indicationsin the plurality of uplink cancellation indications. The wireless devicemay determine the first uplink cancellation indication based on the oneor more parameters.

In an example, the DCI may be a group common DCI; and the receiving theDCI may be based on a common search space.

Uplink cancellation may be a mechanism used for realizing the strictlatency and reliability requirements of the ultra-reliable low-latency(URLLC) applications and services. The base station may transmitdownlink control signaling, using a common downlink signaling,indicating radio resources that are cancelled and indicating that theuplink transmissions that at least partially overlap with the indicatedradio resources are cancelled. Existing control channel monitoringsolutions may be inefficient for reception of the common downlinksignaling. Moreover, existing SCell deactivation procedures may lead tounnecessary SCell deactivation and lead to degraded wireless device andnetwork performance. There is a need to enhance the control channelmonitoring mechanisms and the SCell deactivation procedure. Exampleembodiments enhance the control channel monitoring and the SCelldeactivation procedures.

In an example embodiment as shown in FIG. 23, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. Theconfiguration parameters may comprise uplink cancellation indicationconfiguration parameters. The uplink cancellation configurationparameters may comprise a cancellation indication radio networktemporary identifier (CI-RNTI). The uplink cancellation configurationparameters may be used by the wireless device to monitor a downlinkcontrol channel (e.g., PDCCH) for the CI-RNTI and for receiving acancellation indication downlink control information comprising uplinkcancellation indications. The uplink cancellation configurationparameters may further comprise a parameter indicating a payload size ofthe cancellation indication DCI, one or more parameters for determininga cancellation indication from a plurality of cancellation indicationparameters included in the cancellation indication DCI, one or moreparameters for determining a time and frequency region (e.g., aplurality of radio resources) in which uplink transmissions arecancelled, etc. For example, the uplink cancellation configurationparameters may comprise an offset parameter for determining a symbolfirst symbol (e.g., a starting symbol) of the plurality of radioresources for which the uplink transmissions are cancelled.

The wireless device may monitor a common search space for a controlchannel (e.g., PDCCH) for the CI-RNTI during a time window. The timewindow (e.g., the start time, the end time and/or the duration of thetime window) may be based on a timing of a scheduled uplinktransmission. For example, the end timing of the time window may be anoffset before the timing of the scheduled uplink transmission. In anexample, the scheduled uplink transmission may be a scheduled physicaluplink shared channel (PUSCH) transmission or a scheduled soundingreference signal (SRS) transmission. For example, the wireless devicemay receive a scheduling DCI comprising scheduling information fortransmission of a transport block (TB) via the PUSCH and at the timing.For example, the wireless device may receive a DCI comprising an SRSrequest field, a value of the SRS request field indicating a request forSRS transmission and the SRS transmission may be scheduled at thetiming. In an example, the starting time of the time window may furtherbe based on a first timing of DCI that scheduled the uplink transmission(e.g., the PUSCH or the SRS). For example, the starting time of the timewindow may be an offset from the first timing of the DCI. In an example,the offset may be a configurable parameter (e.g., based on an RRCparameter). In an example, the offset may be based on a processing time(e.g., the processing time of the DCI).

In an example, the scheduled uplink transmission may be scheduledwithout dynamic scheduling, for example may be via a configured grantresource, configured for transmission of a configured grant PUSCH at thetiming, or may be based on a periodic SRS transmission. For example, thewireless device may receive SRS configuration parameters and thetransmission of the SRS or the periodic SRS may be based on the SRSconfiguration parameters. For example, the wireless device may receiveconfigured grant configuration parameters (e.g., periodicity, parametersfor determining configured grant radio resources, etc.) and thetransmission of the scheduled uplink transmission may be via aconfigured grant resource. The wireless device may determine theconfigured grant resource based on the configured grant configurationparameters.

The wireless device may monitor the common search space for the controlchannel (e.g., PDCCH) associated with the CI-RNTI during the time windowand irrespective/regardless of whether the wireless device is in acontinuous reception (DRX) Active Time or not. In an example, thewireless device may receive DRX configuration parameters and maydetermine to be in a DRX Active Time or not to be in a DRX Active Timeduring the time window based on the DRX configuration parameters andusing a DRX procedure. In an example, the wireless device may receiveDRX configuration parameters and may determine to be in the DRX ActiveTime or not to be in the DRX Active Time at least during a portion ofthe time window based on the DRX configuration parameters and using aDRX procedure. The monitoring of the common search space for the controlchannel (e.g., PDCCH) associated with the CI-RNTI during the time windowmay be independent of the DRX state (e.g., whether the wireless devicein the DRX Active Time or not) of the wireless device.

The wireless device may receive a cancellation indication DCI. Thecancellation indication DCI may be associated with the CI-RNTI. Thewireless device may receive the cancellation indication DCI based onmonitoring the common search space for the control channel associatedwith the CI-RNTI. The cancellation indication DCI may comprise aplurality of cancellation indications and the wireless device maydetermine a cancellation indication, in the plurality of cancellationindications, based on the cancellation indication configurationparameters. The cancellation indication, determined based on thecancellation indication DCI and based on the cancellation indicationconfiguration parameters, may indicate a plurality of resources forwhich the uplink transmissions are to be cancelled by the wirelessdevices for which the cancellation indication applies. The plurality ofresources may overlap, at least partially with the first radio resourcesof the scheduled uplink transmission (e.g., the scheduled PUSCH or thescheduled SRS at the timing). Based on the determination that theplurality of resources, indicated by the cancellation indication, atleast partially overlap with the first resources of the scheduled uplinktransmission, the wireless device may cancel the scheduled uplinktransmission.

In an example embodiment as shown in FIG. 24, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. Theconfiguration parameters may comprise uplink cancellation indicationconfiguration parameters. The uplink cancellation configurationparameters may comprise a cancellation indication radio networktemporary identifier (CI-RNTI). The uplink cancellation configurationparameters may be used by the wireless device to monitor a downlinkcontrol channel (e.g., PDCCH) for the CI-RNTI and for receiving acancellation indication downlink control information comprising uplinkcancellation indications. The uplink cancellation configurationparameters may further comprise a parameter indicating a payload size ofthe cancellation indication DCI, one or more parameters for determininga cancellation indication from a plurality of cancellation indicationparameters included in the cancellation indication DCI, one or moreparameters for determining a time and frequency region (e.g., aplurality of radio resources) in which uplink transmissions arecancelled, etc. For example, the uplink cancellation configurationparameters may comprise an offset parameter for determining a symbolfirst symbol (e.g., a starting symbol) of the plurality of radioresources for which the uplink transmissions are cancelled.

The one or more message may comprise configuration parameters of aplurality of cells. The plurality of cells may comprise a primary celland one or more secondary cells comprising a first secondary cell. Theconfiguration parameters of the first secondary cell may comprise avalue of a deactivation timer for the first secondary cell. The wirelessdevice may deactivate the secondary cell based on a SCell deactivationprocedure and based on the deactivation timer of the first secondarycell expiring.

The wireless device may receive a cancellation indication DCI. Thecancellation indication DCI may be associated with the CI-RNTI. Thewireless device may receive the cancellation indication DCI based onmonitoring the common search space for the control channel associatedwith the CI-RNTI. The cancellation indication DCI may comprise aplurality of cancellation indications and the wireless device maydetermine a cancellation indication, in the plurality of cancellationindications, based on the cancellation indication configurationparameters. The cancellation indication, determined based on thecancellation indication DCI and based on the cancellation indicationconfiguration parameters, may indicate a plurality of resources forwhich the uplink transmissions are to be cancelled by the wirelessdevices for which the cancellation indication applies. The plurality ofresources may overlap, at least partially with the first radio resourcesof a scheduled uplink transmission (e.g., a scheduled PUSCH). Based onthe determination that the plurality of resources, indicated by thecancellation indication, at least partially overlap with the firstresources of the scheduled uplink transmission, the wireless device maycancel the scheduled uplink transmission. The wireless device mayfurther start the SCell Deactivation timer, associated with the firstsecondary cell, based on receiving the cancellation indication DCI. Thewireless device may further start the SCell Deactivation timer,associated with the first secondary cell, based on receiving thecancellation indication DCI and based on the cancellation indication DCIindicating cancellation of the scheduled uplink transmission. Thewireless device may use the SCell deactivation procedure and maydeactivate the first secondary cell based on the SCell Deactivationtimer, associated with the first secondary cell, expiring.

In accordance with various exemplary embodiments in the presentdisclosure, a device (e.g., a wireless device, a base station and/oralike) may include one or more processors and may include memory thatmay store instructions. The instructions, when executed by the one ormore processors, cause the device to perform actions as illustrated inthe accompanying drawings and described in the specification. The orderof events or actions, as shown in a flow chart of this disclosure, mayoccur and/or may be performed in any logically coherent order. In someexamples, at least two of the events or actions shown may occur or maybe performed at least in part simultaneously and/or in parallel. In someexamples, one or more additional events or actions may occur or may beperformed prior to, after, or in between the events or actions shown inthe flow charts of the present disclosure.

FIG. 25 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 2510, a wirelessdevice may receive uplink cancellation indication configurationparameters comprising a first radio network temporary identifier (RNTI).At 2520, the wireless device may monitor a common search space, for acontrol channel associated with the first RNTI, in a time window that isbased on a timing of a scheduled uplink transmission and regardless ofbeing in a discontinuous reception (DRX) Active Time or not. At 2530,the wireless device may receive a cancellation indication downlinkcontrol information, associated with the first RNTI, indicatingcancellation of uplink transmissions on first radio resources of thescheduled uplink transmission. At 2540, the wireless device may cancelthe scheduled uplink transmission.

In an example embodiment, the wireless device may further receive adownlink control information comprising scheduling information for thescheduled uplink transmission at 2520. In an example embodiment, thetime window may further be based on a first timing of the downlinkcontrol information. In an example embodiment, a starting time of thetime window may be an offset from the first timing of the downlinkcontrol information. In an example embodiment, the wireless device mayfurther receive, at 2510, a configuration parameter indicating theoffset.

In an example embodiment, the scheduled uplink transmission, at 2520,may be via a physical uplink shared channel (PUSCH).

In an example embodiment, the scheduled uplink transmission, at 2520,may be a sounding reference signal (SRS).

In an example embodiment, the cancellation indication downlink controlinformation, received at 2530, may comprise an uplink cancellationindication indicating cancellation of uplink transmissions on aplurality of radio resources comprising the first radio resources.

In an example embodiment, the uplink cancellation indicationconfiguration parameters, received at 2510, may comprise an offsetparameter indicating a number of symbols from the cancellationindication downlink control information, received at 2530, fordetermining a first symbol of the plurality of radio resources.

In an example embodiment, an end time of the time window, at 2520, maybe an offset before the timing of the scheduled uplink transmission. Inan example, the offset may be based on a processing time.

In an example embodiment, the wireless device may further receive, at2510, periodic resource configuration parameters, wherein the scheduleduplink transmission may be based on the periodic resource configurationparameters. In an example embodiment, the periodic resourceconfiguration parameters comprise at least one of: configured grantconfiguration parameters; and periodic sounding reference signal (SRS)configuration parameters.

In an example embodiment, the wireless device may further receive, at2510, DRX configuration parameters, wherein: the DRX configurationparameters comprise a value of a first DRX timer; and the wirelessdevice is, at 2520, in the DRX Active Time based on the first DRX timerrunning.

In an example embodiment, the wireless device may further receive, at2510, DRX configuration parameters. The wireless device may determinethat the wireless device is not in the DRX Active Time, at 2520, basedon the DRX configuration parameters.

FIG. 26 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 2610, a wirelessdevice may receive: uplink cancellation indication configurationparameters comprising a first radio network temporary identifier (RNTI);and configuration parameters of a secondary cell comprising a value of adeactivation timer. At 2620, the wireless device may receive acancellation indication downlink control information, associated withthe first RNTI, indicating cancellation of a scheduled uplinktransmission on the secondary cell. At 2630, the wireless device maystart the deactivation timer, with the value, based on receiving thecancellation indication downlink control information. At 2640, thewireless device may deactivate the secondary cell based on thedeactivation timer expiring.

Various exemplary embodiments of the disclosed technology are presentedas example implementations and/or practices of the disclosed technology.The exemplary embodiments disclosed herein are not intended to limit thescope. Persons of ordinary skill in the art will appreciate that variouschanges can be made to the disclosed embodiments without departure fromthe scope. After studying the exemplary embodiments of the disclosedtechnology, alternative aspects, features and/or embodiments will becomeapparent to one of ordinary skill in the art. Without departing from thescope, various elements or features from the exemplary embodiments maybe combined to create additional embodiments. The exemplary embodimentsare described with reference to the drawings. The figures and theflowcharts that demonstrate the benefits and/or functions of variousaspects of the disclosed technology are presented for illustrationpurposes only. The disclosed technology can be flexibly configuredand/or reconfigured such that one or more elements of the disclosedembodiments may be employed in alternative ways. For example, an elementmay be optionally used in some embodiments or the order of actionslisted in a flowchart may be changed without departure from the scope.

An example embodiment of the disclosed technology may be configured tobe performed when deemed necessary, for example, based on one or moreconditions in a wireless device, a base station, a radio and/or corenetwork configuration, a combination thereof and/or alike. For example,an example embodiment may be performed when the one or more conditionsare met. Example one or more conditions may be one or moreconfigurations of the wireless device and/or base station, traffic loadand/or type, service type, battery power, a combination of thereofand/or alike. In some scenarios and based on the one or more conditions,one or more features of an example embodiment may be implementedselectively.

In this disclosure, the articles “a” and “an” used before a group of oneor more words are to be understood as “at least one” or “one or more” ofwhat the group of the one or more words indicate. The use of the term“may” before a phrase is to be understood as indicating that the phraseis an example of one of a plurality of useful alternatives that may beemployed in an embodiment in this disclosure.

In this disclosure, an element may be described using the terms“comprises”, “includes” or “consists of” in combination with a list ofone or more components. Using the terms “comprises” or “includes”indicates that the one or more components are not an exhaustive list forthe description of the element and do not exclude components other thanthe one or more components. Using the term “consists of” indicates thatthe one or more components is a complete list for description of theelement. In this disclosure, the term “based on” is intended to mean“based at least in part on”. The term “based on” is not intended to mean“based only on”. In this disclosure, the term “and/or” used in a list ofelements indicates any possible combination of the listed elements. Forexample, “X, Y, and/or Z” indicates X; Y; Z; X and Y; X and Z; Y and Z;or X, Y, and Z.

Some elements in this disclosure may be described by using the term“may” in combination with a plurality of features. For brevity and easeof description, this disclosure may not include all possiblepermutations of the plurality of features. By using the term “may” incombination with the plurality of features, it is to be understood thatall permutations of the plurality of features are being disclosed. Forexample, by using the term “may” for description of an element with fourpossible features, the element is being described for all fifteenpermutations of the four possible features. The fifteen permutationsinclude one permutation with all four possible features, fourpermutations with any three features of the four possible features, sixpermutations with any two features of the four possible features andfour permutations with any one feature of the four possible features.

Although mathematically a set may be an empty set, the term set used inthis disclosure is a nonempty set. Set B is a subset of set A if everyelement of set B is in set A. Although mathematically a set has an emptysubset, a subset of a set is to be interpreted as a non-empty subset inthis disclosure. For example, for set A={subcarrier1, subcarrier2}, thesubsets are {subcarrier1}, {subcarrier2} and {subcarrier1, subcarrier2}.

In this disclosure, the phrase “based on” may be used equally with“based at least on” and what follows “based on” or “based at least on”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure. The phrase “in response to”may be used equally with “in response at least to” and what follows “inresponse to” or “in response at least to” indicates an example of one ofplurality of useful alternatives that may be used in an embodiment inthis disclosure. The phrase “depending on” may be used equally with“depending at least on” and what follows “depending on” or “depending atleast on” indicates an example of one of plurality of usefulalternatives that may be used in an embodiment in this disclosure. Thephrases “employing” and “using” and “employing at least” and “using atleast” may be used equally in this in this disclosure and what follows“employing” or “using” or “employing at least” or “using at least”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure.

The example embodiments disclosed in this disclosure may be implementedusing a modular architecture comprising a plurality of modules. A modulemay be defined in terms of one or more functions and may be connected toone or more other elements and/or modules. A module may be implementedin hardware, software, firmware, one or more biological elements (e.g.,an organic computing device and/or a neurocomputer) and/or a combinationthereof and/or alike. Example implementations of a module may be assoftware code configured to be executed by hardware and/or a modelingand simulation program that may be coupled with hardware. In an example,a module may be implemented using general-purpose or special-purposeprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, application-specific integrated circuits (ASICs),programmable logic devices (PLDs) and/or alike. The hardware may beprogrammed using machine language, assembly language, high-levellanguage (e.g., Python, FORTRAN, C, C++ or the like) and/or alike. In anexample, the function of a module may be achieved by using a combinationof the mentioned implementation methods.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice: cancellation indication configuration parameters comprising afirst configuration parameter indicating a first radio network temporaryidentifier (RNTI); and a second configuration parameter indicating avalue of a deactivation timer of a secondary cell; receiving acancellation indication downlink control information, associated withthe first RNTI, indicating cancellation of an uplink transmission on thesecondary cell; based on receiving the cancellation indication downlinkcontrol information, starting the deactivation timer with the value; anddeactivating the secondary cell based on the deactivation timerexpiring.
 2. The method of claim 1, further comprising receiving a firstdownlink control information comprising scheduling information for theuplink transmission.
 3. The method of claim 1, further comprisingreceiving third configuration parameters of a configured grantconfiguration, wherein the uplink transmission is based on the thirdconfiguration parameters.
 4. The method of claim 3, further comprisingreceiving an activation downlink control information indicatingactivation of the configured grant configuration.
 5. The method of claim1, further comprising cancelling the uplink transmission based on thereceiving the cancellation indication downlink control information. 6.The method of claim 5, wherein the cancelling the uplink transmission isfurther based on the cancellation indication configuration parameters.7. The method of claim 5, wherein: the cancellation indication downlinkcontrol information comprises a plurality of cancellation indicationscomprising a first cancellation indication; and the cancelling theuplink transmission is based on the first cancellation indication. 8.The method of claim 7, further comprising determining the firstcancellation indication in the plurality of cancellation indications. 9.The method of claim 8, wherein the determining is based on thecancellation indication configuration parameters.
 10. The method ofclaim 1, wherein the cancellation indication configuration parametersindicate radio resources in which uplink transmission is cancelled. 11.A wireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive: cancellation indication configurationparameters comprising a first configuration parameter indicating a firstradio network temporary identifier (RNTI); and a second configurationparameter indicating a value of a deactivation timer of a secondarycell; receive a cancellation indication downlink control information,associated with the first RNTI, indicating cancellation of an uplinktransmission on the secondary cell; based on receiving the cancellationindication downlink control information, start the deactivation timerwith the value; and deactivate the secondary cell based on thedeactivation timer expiring.
 12. The wireless device of claim 11,wherein the instructions, when executed by the one or more processors,further cause the wireless device to receive a first downlink controlinformation comprising scheduling information for the uplinktransmission.
 13. The wireless device of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to receive third configuration parameters of aconfigured grant configuration, wherein the uplink transmission is basedon the third configuration parameters.
 14. The wireless device of claim13, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to receive an activationdownlink control information indicating activation of the configuredgrant configuration.
 15. The wireless device of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to cancel the uplink transmission based on thereceiving the cancellation indication downlink control information. 16.The wireless device of claim 15, wherein cancelling the uplinktransmission is further based on the cancellation indicationconfiguration parameters.
 17. The wireless device of claim 15, wherein:the cancellation indication downlink control information comprises aplurality of cancellation indications comprising a first cancellationindication; and cancelling the uplink transmission is based on the firstcancellation indication.
 18. The wireless device of claim 17, whereinthe instructions, when executed by the one or more processors, furthercause the wireless device to determine the first cancellation in theplurality of cancellation indications.
 19. The wireless device of claim18, wherein determining the first cancellation indication is based onthe cancellation indication configuration parameters.
 20. A systemcomprising: a base station; and a wireless device comprising: one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the wireless device to: receive fromthe base station: cancellation indication configuration parameterscomprising a first configuration parameter indicating a first radionetwork temporary identifier (RNTI); and a second configurationparameter indicating a value of a deactivation timer of a secondarycell; receive a cancellation indication downlink control information,associated with the first RNTI, indicating cancellation of an uplinktransmission on the secondary cell; based on receiving the cancellationindication downlink control information, start the deactivation timerwith the value; and deactivate the secondary cell based on thedeactivation timer expiring.